00:00:12.516 --> 00:00:13.006 Ah.
00:00:12.666 --> 00:00:13.396 Good question.
00:00:13.806 --> 00:00:17.056 We might want a separate box just because.
00:00:16.116 --> 00:00:16.586 Yeah.
00:00:19.246 --> 00:00:22.532 Will want to be able to search on multiple fields at the same
00:00:22.532 --> 00:00:25.606 time, which you can't do unless you have multiple inputs.
00:00:26.056 --> 00:00:28.630 Yeah. So I would say for this one, we wouldn't have location
00:00:28.630 --> 00:00:31.247 in it, it would just be by title company or keyword. And then
00:00:31.247 --> 00:00:33.653 once you get the catalog, there'd be the location filter
00:00:33.653 --> 00:00:36.058 on the left hand side. And I think that was the original
00:00:36.058 --> 00:00:37.536 scope for this feature anyway, so.
00:00:39.506 --> 00:00:44.982 OK. So we'll forward title company keywords. I mean look at
00:00:44.982 --> 00:00:45.986 the ticket.
00:00:46.986 --> 00:00:48.506 Because the the original.
00:00:49.816 --> 00:00:53.391 The original implementation that I did had a field had a separate
00:00:53.391 --> 00:00:56.859 input here on the home page for location. There were two inputs
00:00:56.859 --> 00:01:00.163 here and that was acts. I just wanted to check the ticket to
00:01:00.163 --> 00:01:03.306 make sure that I thought had pulled up to make sure that.
00:01:05.626 --> 00:01:08.956 I don't have to have anything on the homepage for location.
00:01:12.666 --> 00:01:13.076 No.
00:01:18.246 --> 00:01:18.866 Great enough.
00:01:29.176 --> 00:01:30.286 And I'll pay you.
00:01:39.246 --> 00:01:40.786 It search functionality.
00:01:45.716 --> 00:01:50.123 User can serve for job listings by location, keywords, title and
00:01:50.123 --> 00:01:50.666 company.
00:01:52.166 --> 00:01:52.736 Please search.
00:01:54.306 --> 00:01:58.757 Circulations, etcetera, keywords are to include certifications
00:01:58.757 --> 00:01:59.676 and etcetera.
00:02:01.076 --> 00:02:05.585 As of right now, the keywords there is a keywords field on the
00:02:05.585 --> 00:02:09.951 form to create a job opening that stores keywords in the SEO
00:02:09.951 --> 00:02:10.596 keywords.
00:02:11.296 --> 00:02:15.948 Off call them on the job opening so certifications. I don't know
00:02:15.948 --> 00:02:20.171 that that's gonna be cause certifications instead of being
00:02:20.171 --> 00:02:21.746 a text box or a model.
00:02:24.076 --> 00:02:25.356 I don't know if that's going to.
00:02:27.986 --> 00:02:29.256 Not be possible, right?
00:02:29.686 --> 00:02:31.786 Uh to include keywords off?
00:02:30.236 --> 00:02:33.672 We can index it on to. Yeah, we can. We can. We can make things
00:02:33.672 --> 00:02:36.679 work. However we need to. The index doesn't necessarily
00:02:36.679 --> 00:02:40.223 constrain like the the structure of the data in the index doesn't
00:02:40.223 --> 00:02:43.498 need to be constrained to the structure of the physical self
00:02:43.498 --> 00:02:46.881 data model or anything. So if we want to store a smattering of
00:02:44.716 --> 00:02:45.876 Models OK.
00:02:46.881 --> 00:02:50.425 information off of related stuff to make it to make this work the
00:02:50.425 --> 00:02:53.056 way that the client wants it to, we can do that.
00:02:54.286 --> 00:02:54.756 OK.
00:02:55.106 --> 00:02:57.566 Just like how you can search products by categories.
00:02:55.156 --> 00:02:55.746 So.
00:02:57.906 --> 00:02:58.546 Yep.
00:02:59.396 --> 00:03:00.266 Uh.
00:03:00.386 --> 00:03:00.676 So.
00:03:01.846 --> 00:03:02.826 Alright, so let's see here.
00:03:02.306 --> 00:03:06.604 And also there is another thing tied into this, the job title
00:03:06.604 --> 00:03:10.695 search is supposed to be case specific or it it is working
00:03:10.695 --> 00:03:15.063 this case sensitive but isn't that's a bug ticket that I have?
00:03:15.063 --> 00:03:16.866 I don't know that that is.
00:03:15.626 --> 00:03:19.207 So it's not supposed to be case sensitive or it should be case
00:03:18.726 --> 00:03:23.386 Yes, it's not supposed to be case sensitive. And it is, yeah.
00:03:19.207 --> 00:03:19.776 sensitive.
00:03:21.246 --> 00:03:23.783 OK, that's what I thought that that makes sense is that it
00:03:23.783 --> 00:03:25.116 wouldn't be case sensitive, OK.
00:03:25.166 --> 00:03:25.596 Yeah.
00:03:26.376 --> 00:03:26.846 Cool.
00:03:26.966 --> 00:03:27.586 Uh.
00:03:27.936 --> 00:03:28.566 Umm.
00:03:28.616 --> 00:03:29.276 So.
00:03:30.766 --> 00:03:31.956 On the.
00:03:34.806 --> 00:03:39.020 For the dump reader, like I said, all of the fields are in
00:03:39.020 --> 00:03:43.234 the dump reader. All of the fields are on the search model
00:03:43.234 --> 00:03:44.806 with the exception of.
00:03:46.446 --> 00:03:48.656 Yet the deal distances on the search model.
00:03:49.676 --> 00:03:51.896 Umm and the indexer.
00:03:52.596 --> 00:03:57.976 Has coordinates as your keywords company name, job title. OK so.
00:03:59.016 --> 00:04:00.126 From here.
00:04:01.376 --> 00:04:02.386 What needs to be done?
00:04:03.096 --> 00:04:06.948 So we need to make sure, number one that those keywords company
00:04:06.948 --> 00:04:10.079 name, job title, name, coordinates and all that are
00:04:10.079 --> 00:04:13.811 still being indexed or stored into the index and that's gonna
00:04:13.811 --> 00:04:15.136 be on the dump reader.
00:04:17.006 --> 00:04:17.386 OK.
00:04:18.666 --> 00:04:22.017 Alright, so let's make sure that we're actually reading it out,
00:04:19.016 --> 00:04:19.256 But.
00:04:22.017 --> 00:04:25.211 which is gonna be that context dot job openings a little bit
00:04:25.211 --> 00:04:28.196 lower. There's a big giant select that starts online 45.
00:04:28.746 --> 00:04:29.206 Yeah.
00:04:29.686 --> 00:04:33.786 OK, so we are reading out SEO keywords description name.
00:04:30.316 --> 00:04:31.216 Threaten.
00:04:34.866 --> 00:04:36.716 Excuse me, title.
00:04:37.386 --> 00:04:41.129 A company name. Yeah. OK. Looks like we've got. Looks like we
00:04:41.129 --> 00:04:43.786 got everything that we want being read out.
00:04:44.356 --> 00:04:49.506 Do we want other address fields like ZIP code or state or?
00:04:50.266 --> 00:04:53.068 In this case, the only thing that we're actually reading out
00:04:50.456 --> 00:04:50.866 Bunch.
00:04:53.068 --> 00:04:54.446 is the latitude and longitude.
00:04:57.326 --> 00:05:00.775 And uh, the Geo, the Geo distance filtering, uh works off
00:05:00.775 --> 00:05:02.916 of latitude, longitude and elastic.
00:05:04.276 --> 00:05:04.906 Umm.
00:05:07.936 --> 00:05:09.286 OK wait, scroll up a little bit.
00:05:10.876 --> 00:05:13.406 Umm OK.
00:05:15.416 --> 00:05:20.484 Uh, yeah. There we go. So lines 102 through 107 are making sure.
00:05:20.484 --> 00:05:25.318 So we read the contact ID out and if we have a contact ID but
00:05:25.318 --> 00:05:29.763 no latitude or longitude is set, then we try to backfill
00:05:29.763 --> 00:05:32.726 latitude, longitude onto the address.
00:05:33.816 --> 00:05:34.406 Umm.
00:05:41.296 --> 00:05:44.506 Can you F-12 on that ensure lat long on address?
00:05:42.406 --> 00:05:42.716 Well.
00:05:45.656 --> 00:05:45.896 Yep.
00:05:50.706 --> 00:05:51.386 Hmm.
00:05:50.806 --> 00:05:52.486 Why did that jump up there?
00:05:53.186 --> 00:05:55.206 That's a great question. Why did it do that?
00:05:56.746 --> 00:05:57.476 No.
00:05:57.526 --> 00:05:57.976 There we go.
00:05:59.206 --> 00:05:59.856 Yeah.
00:06:02.366 --> 00:06:06.620 Yeah, contacts getting the address and then if address
00:06:06.620 --> 00:06:09.096 stuff all launch to is not null.
00:06:10.316 --> 00:06:14.051 Return already set for the address, else if address is not
00:06:14.051 --> 00:06:17.723 null, we're gonna set the longitude and latitude based on
00:06:17.723 --> 00:06:18.736 the postal code.
00:06:20.746 --> 00:06:22.936 And of course is not equal to null.
00:06:25.196 --> 00:06:27.546 Yeah, that looks right. Right. We're going back.
00:06:25.626 --> 00:06:25.866 Hmm.
00:06:27.496 --> 00:06:31.649 Yeah. So that all looks that all looks correct. What I'm what,
00:06:31.649 --> 00:06:35.539 I'm not entirely sure of. If we scroll up a little bit, it
00:06:35.539 --> 00:06:36.726 doesn't look like.
00:06:37.566 --> 00:06:38.456 It actually.
00:06:39.636 --> 00:06:42.172 Rereads that back out of the database, and we're not
00:06:42.172 --> 00:06:44.086 returning it from this function either.
00:06:45.206 --> 00:06:45.646 No.
00:06:47.426 --> 00:06:50.560 So let's scroll back up, collapse the handle. Custom
00:06:50.560 --> 00:06:51.566 suggests for now.
00:06:51.786 --> 00:06:52.086 Yeah.
00:06:53.396 --> 00:06:54.856 Not worried about that for the moment.
00:06:55.576 --> 00:06:56.896 Umm, scroll up a little bit.
00:06:59.796 --> 00:07:01.096 Yeah. OK. So right there.
00:07:02.846 --> 00:07:07.354 We backs, we backfill that data into the database if it wasn't
00:07:07.354 --> 00:07:11.577 already in there, but then we don't actually store it back
00:07:11.577 --> 00:07:15.871 onto the version. So we should probably do is let's go into
00:07:12.756 --> 00:07:13.196 Umm.
00:07:15.871 --> 00:07:17.016 that real quick.
00:07:17.676 --> 00:07:20.016 That ensure lat long on address yeah.
00:07:17.886 --> 00:07:19.256 Into the lat long again.
00:07:19.946 --> 00:07:20.466 Yeah.
00:07:20.936 --> 00:07:23.595 Of one set back to the version we should pass the version
00:07:21.046 --> 00:07:21.656 And then.
00:07:23.595 --> 00:07:25.016 instead of just the contact ID.
00:07:25.026 --> 00:07:27.853 Yeah, I was just gonna have this return the lat, long and a
00:07:27.853 --> 00:07:28.136 tuple.
00:07:28.796 --> 00:07:29.466 Umm.
00:07:29.036 --> 00:07:29.416 OK.
00:07:30.386 --> 00:07:33.801 And then write it onto there over there. So then instead of
00:07:33.801 --> 00:07:36.933 a, it's not a, it's not an array one like that, it's a
00:07:36.933 --> 00:07:37.616 parentheses.
00:07:38.836 --> 00:07:43.086 Oh yeah, so it would be it. Is it just?
00:07:39.676 --> 00:07:44.842 Yeah, and then it'll be decimal, it'll be decimal, decimal at
00:07:44.842 --> 00:07:45.926 decimal long.
00:07:48.206 --> 00:07:51.116 Yeah, OK. Can't be long because long is also a data type.
00:07:48.566 --> 00:07:49.236 OK.
00:07:51.066 --> 00:07:51.676 Umm.
00:07:52.816 --> 00:07:53.256 Uh.
00:07:53.496 --> 00:07:54.436 LNG.
00:07:55.326 --> 00:07:59.726 Yeah, that's gonna write out the fully qualified name, so.
00:07:57.856 --> 00:08:03.232 Yeah. OK. And then just return address dot latitude address dot
00:08:03.232 --> 00:08:05.416 longitude and parentheses.
00:08:06.746 --> 00:08:07.026 Yep.
00:08:19.806 --> 00:08:22.216 Other nullable. So this is gonna be nullable.
00:08:24.426 --> 00:08:28.650 No, that's fine. Uh, keep it not nullable and then just put a dot
00:08:24.686 --> 00:08:25.456 Or just.
00:08:28.650 --> 00:08:32.874 value on the end of those. We're already. We're already asserting
00:08:32.874 --> 00:08:36.906 on the line above that they're not null, and this should never
00:08:34.136 --> 00:08:34.956 That's true, yeah.
00:08:36.906 --> 00:08:38.186 return. No, I think.
00:08:38.866 --> 00:08:41.182 Actually, no. Yeah, go ahead and make them nullable up there
00:08:41.182 --> 00:08:43.460 because there's a chance that we don't have a zip code that
00:08:43.460 --> 00:08:43.916 corresponds.
00:08:45.306 --> 00:08:47.546 Umm, like not a real zip code.
00:08:48.356 --> 00:08:50.686 Yeah. Or we just don't have the data for it.
00:08:51.676 --> 00:08:56.226 In which case this could return null, which would be fine.
00:08:56.576 --> 00:08:58.246 Because we don't have a default that long.
00:08:58.726 --> 00:09:02.798 Yeah. OK. And then inside that if chords is not equal to null
00:09:02.798 --> 00:09:06.806 then after context dot save unit of work you'll do a return.
00:09:07.606 --> 00:09:10.786 Uh cords dot latitude chords dot long longitude.
00:09:15.596 --> 00:09:17.846 Then after that you'll just do return null, null.
00:09:18.036 --> 00:09:19.966 Yep, at the very bottom.
00:09:20.896 --> 00:09:23.756 Hmm. Yeah, bottom of this.
00:09:22.116 --> 00:09:23.056 Of the method dear.
00:09:34.706 --> 00:09:34.986 Yeah.
00:09:42.326 --> 00:09:46.406 OK. And then back up at the call site for this.
00:09:48.966 --> 00:09:50.106 Ohh.
00:09:50.226 --> 00:09:51.126 A little bit lower.
00:09:54.216 --> 00:09:55.126 A little bit lower.
00:09:57.026 --> 00:09:57.296 Yeah.
00:09:57.076 --> 00:10:00.579 Right there. OK. On the line before that, just do VAR and
00:09:59.186 --> 00:09:59.756 Yeah.
00:10:00.579 --> 00:10:03.961 then parenthesis, sorry not the line before that at the
00:10:03.961 --> 00:10:06.136 beginning of that line. I misspoke.
00:10:05.976 --> 00:10:06.466 OK.
00:10:07.036 --> 00:10:07.636 Umm.
00:10:07.256 --> 00:10:08.256 That's OK.
00:10:08.966 --> 00:10:14.578 You're good. Yeah. Between that line VAR and then print theses
00:10:14.578 --> 00:10:15.826 lat comma LNG.
00:10:18.306 --> 00:10:23.876 Equals that and then do after that version dot latitude equals
00:10:23.876 --> 00:10:27.236 lat version dot longitude equals LNG.
00:10:34.996 --> 00:10:35.766 Yes, I'm calling.
00:10:38.706 --> 00:10:40.456 Oh, it doesn't like that. Why?
00:10:42.236 --> 00:10:43.346 Ohh I see why.
00:10:46.396 --> 00:10:47.766 Because that's a.
00:10:48.576 --> 00:10:51.086 Part of the iterator and you can't set values on it.
00:10:50.846 --> 00:10:51.396 Umm.
00:10:52.116 --> 00:10:52.616 Yeah.
00:10:53.346 --> 00:10:54.816 That's sorry, just do.
00:10:56.486 --> 00:11:01.699 Uh on the line? Click at the end of line 101 and then create a
00:11:01.699 --> 00:11:04.596 create 2 new like local variables.
00:11:04.836 --> 00:11:07.896 Uh, yeah, that are like.
00:11:09.486 --> 00:11:14.476 Yeah, var latitude to use or or like lat to use or whatever.
00:11:17.416 --> 00:11:19.476 Equals version dot latitude.
00:11:21.786 --> 00:11:23.406 Yeah. And then same thing for longitude.
00:11:37.026 --> 00:11:39.626 Sign this to these locals.
00:11:40.616 --> 00:11:41.136 Yes.
00:11:41.896 --> 00:11:45.943 And then instead of checking against, uh, actually easy
00:11:45.943 --> 00:11:50.279 easiest way to do this. Uh, undo what you just did and then
00:11:50.279 --> 00:11:53.676 highlight the version dot latitude online 105.
00:11:54.416 --> 00:11:57.102 Uh, not including the exclamation point at the
00:11:57.102 --> 00:12:00.588 beginning, just the yeah. And then hold shift, alt and press
00:12:00.588 --> 00:12:01.446 the period key.
00:12:02.566 --> 00:12:05.511 And then continue holding shift Alt and just keep pressing
00:12:05.511 --> 00:12:08.456 period until it highlights the next one more time I think.
00:12:09.696 --> 00:12:13.879 OK, now type LAT to use and it'll replace all of those with
00:12:13.879 --> 00:12:14.646 lat to use.
00:12:16.856 --> 00:12:19.796 A when it highlights all them, you could have just, uh, yeah.
00:12:18.456 --> 00:12:18.936 Ohh.
00:12:20.136 --> 00:12:20.626 Yeah.
00:12:20.886 --> 00:12:22.436 It's all right clicks like this too.
00:12:25.256 --> 00:12:26.126 I just.
00:12:27.076 --> 00:12:27.776 That's not right.
00:12:27.196 --> 00:12:28.556 You got use our.
00:12:32.056 --> 00:12:35.426 There we go. OK. And then the same for long to use as well.
00:12:39.106 --> 00:12:43.026 Right here to here. You did shift all period.
00:12:40.716 --> 00:12:43.836 Yeah. And then shift alt. Yep.
00:12:44.606 --> 00:12:44.916 OK.
00:12:45.396 --> 00:12:48.206 And then one more Yep. OK. And then long to use.
00:12:46.076 --> 00:12:46.626 Yeah.
00:12:52.686 --> 00:12:53.416 Yeah, that's right.
00:12:55.286 --> 00:12:56.796 Yeah. Perfect.
00:12:57.546 --> 00:12:58.406 Umm.
00:12:59.376 --> 00:13:01.286 And that will store those into.
00:13:02.776 --> 00:13:03.746 Into.
00:13:04.906 --> 00:13:07.986 That on the coordinates for the INDEXABLE model.
00:13:08.686 --> 00:13:11.783 OK, so that makes sure that we actually correctly backfill
00:13:09.076 --> 00:13:09.436 It.
00:13:11.783 --> 00:13:12.046 that.
00:13:12.996 --> 00:13:15.586 To clarify, what does shipped period do?
00:13:13.076 --> 00:13:13.636 Umm.
00:13:16.886 --> 00:13:21.459 Shift alt period selects the next instance of whatever you
00:13:21.459 --> 00:13:26.266 have highlighted and and does multi like multi caret editing.
00:13:22.796 --> 00:13:23.746 Yeah.
00:13:27.446 --> 00:13:30.496 This is what I was asking you about earlier, Brendan. When I
00:13:30.496 --> 00:13:33.496 say control B, did it Visual Studio code? How did we do it?
00:13:32.456 --> 00:13:36.208 Ohh yeah, yeah, yeah. Control D is the same thing in VS code and
00:13:34.286 --> 00:13:34.776 Yeah.
00:13:36.208 --> 00:13:38.806 Full Visual Studio. It's shift, alt, period.
00:13:39.366 --> 00:13:40.486 Yeah, I knew it was.
00:13:39.486 --> 00:13:42.391 I was just trying to do that on mine and it highlighted the
00:13:42.391 --> 00:13:45.394 other words, but when I type it doesn't change all of them at
00:13:45.394 --> 00:13:45.636 once.
00:13:46.136 --> 00:13:46.356 Hmm.
00:13:47.876 --> 00:13:48.466 Yeah, that's all.
00:13:48.176 --> 00:13:48.866 Interesting.
00:13:51.296 --> 00:13:52.626 OK. Well, no big deal.
00:13:51.816 --> 00:13:52.336 Ah.
00:13:53.276 --> 00:13:57.196 Yeah, we got the back feeling from the address model now.
00:13:57.046 --> 00:14:00.303 Yeah. So that should that should make sure that that happens
00:14:00.303 --> 00:14:03.668 consistently and we are storing the coordinate. We are storing
00:14:03.668 --> 00:14:07.193 all the other stuff we need. OK, so that's good. So we can now we
00:14:07.193 --> 00:14:10.557 can move into the search model, you've got an extra blank line
00:14:10.557 --> 00:14:11.786 111 in the dump reader.
00:14:12.866 --> 00:14:14.746 Just grab that while we're in here.
00:14:16.036 --> 00:14:16.356 Yeah.
00:14:16.466 --> 00:14:19.616 Yeah, alright. Uh, in the search module now.
00:14:20.896 --> 00:14:25.412 Umm, right up here in this uh matching prefix by company name
00:14:25.412 --> 00:14:26.286 by whatever.
00:14:27.196 --> 00:14:27.576 Mm-hmm.
00:14:27.686 --> 00:14:31.561 Uh, so screw up a little bit. There's SEO keywords, the
00:14:31.561 --> 00:14:32.876 there's custom key.
00:14:33.906 --> 00:14:39.134 And the by Dave, I think we want to reenable this by job title
00:14:39.134 --> 00:14:39.466 one.
00:14:41.916 --> 00:14:45.189 Or well, actually, no, I think they don't. They didn't want it
00:14:45.189 --> 00:14:48.411 to be like fuzzy matching on the job title. They wanted it to
00:14:48.411 --> 00:14:51.685 only match exactly. And we'll just have to figure out why it's
00:14:51.685 --> 00:14:54.076 being why it's it's. It's a little too exact.
00:14:55.266 --> 00:14:58.555 With the Bing case specific, we may need to UM like 2 lower it
00:14:58.555 --> 00:15:01.741 when it goes into the index and the dump reader and then two
00:15:01.741 --> 00:15:04.717 lower the query as well. Whenever we do the compare, but
00:15:04.717 --> 00:15:07.746 we'll have to figure out where that's actually happening.
00:15:08.596 --> 00:15:11.006 That being said, keep moving.
00:15:12.076 --> 00:15:13.946 Uh, Scroll down a little bit more.
00:15:20.456 --> 00:15:23.156 So we don't have a, we don't have a region in this for.
00:15:24.046 --> 00:15:25.666 Geolocation. Is that OK?
00:15:26.046 --> 00:15:28.913 That's the GL single query modification. That's a little
00:15:28.913 --> 00:15:29.416 bit lower.
00:15:30.186 --> 00:15:33.383 Geo distance single query modification? Yeah, so that
00:15:31.086 --> 00:15:32.146 Ohh yeah OK.
00:15:33.383 --> 00:15:36.876 would be the next. The next piece that we'd want to check.
00:15:38.576 --> 00:15:42.085 There's a couple of ways that that could potentially be messed
00:15:42.085 --> 00:15:45.539 up, which would be that the form isn't submitting latitude or
00:15:45.539 --> 00:15:46.096 longitude.
00:15:52.376 --> 00:15:56.276 And that that would be, yeah. So that would be the thing that we
00:15:52.736 --> 00:15:53.976 Yeah, I'm not. I don't know.
00:15:56.016 --> 00:15:56.776 We could check it.
00:15:56.276 --> 00:15:57.656 need to check is, yeah.
00:15:58.556 --> 00:16:01.207 So let's let's go ahead and keep everything off and then go ahead
00:16:01.207 --> 00:16:03.738 and rebuild real quick. Since we made some changes, we want to
00:16:03.738 --> 00:16:05.426 make sure that we'll actually be able to.
00:16:07.856 --> 00:16:09.026 See everything here.
00:16:18.886 --> 00:16:22.136 So if the form is submitting Latin law.
00:16:26.696 --> 00:16:27.786 This should be good, right?
00:16:30.546 --> 00:16:35.416 In theory, yes, because there's definitely did work at one point
00:16:32.526 --> 00:16:33.106 OK.
00:16:35.416 --> 00:16:36.016 for the.
00:16:36.876 --> 00:16:40.534 Uh for the distance querying, but I don't know if there's been
00:16:40.534 --> 00:16:44.309 any other changes in the rest of the code that would make it not
00:16:44.309 --> 00:16:46.806 work anymore or anything, so that will be.
00:16:48.836 --> 00:16:51.186 That will be what we're hoping to figure out.
00:17:12.726 --> 00:17:15.760 And just for sanity, can you go to the output tab on the bottom
00:17:15.760 --> 00:17:16.566 of Visual Studio?
00:17:18.516 --> 00:17:21.346 So we can watch the letters drift by.
00:17:25.106 --> 00:17:26.176 This makes me feel better.
00:17:48.096 --> 00:17:49.326 Yes, think about the rainbow.
00:17:50.526 --> 00:17:50.866 Have.
00:17:52.006 --> 00:17:52.536 Extension.
00:17:54.016 --> 00:17:56.206 That's nice. I like being able to see the uh.
00:17:57.906 --> 00:17:59.496 The indentation more clearly.
00:18:01.376 --> 00:18:04.736 It takes some getting used to. I just turned. I just installed it
00:18:04.736 --> 00:18:05.246 yesterday.
00:18:05.896 --> 00:18:08.913 Yeah, I've seen a handful of people with it. I'm just too
00:18:06.556 --> 00:18:07.296 Like it was yesterday.
00:18:08.913 --> 00:18:10.266 lazy to set up extensions.
00:18:12.496 --> 00:18:13.076 Yeah.
00:18:30.126 --> 00:18:33.323 This will be a great video to turn into a nuclear Neal
00:18:33.323 --> 00:18:36.696 article, cause it's something that comes up fairly often.
00:18:38.176 --> 00:18:40.806 Making new Elasticsearch fields and such.
00:18:41.206 --> 00:18:41.556 Mm-hmm.
00:18:52.096 --> 00:18:52.566 Spanish.
00:18:53.776 --> 00:18:56.206 My end, I mean Incognito, that's why.
00:19:01.216 --> 00:19:02.396 Yeah, test seeker.
00:19:17.666 --> 00:19:19.106 You know, if we do.
00:19:20.616 --> 00:19:22.346 Like uh, manager?
00:19:28.266 --> 00:19:31.625 We have a couple for manager. The company name is Premium
00:19:31.625 --> 00:19:34.926 company and premium company name. So I clear the filter.
00:19:37.736 --> 00:19:38.296 Scream.
00:19:39.036 --> 00:19:40.156 Yeah.
00:19:44.476 --> 00:19:47.716 There's premium company, so it's an exact match, right?
00:19:55.406 --> 00:19:56.016 Umm.
00:19:58.876 --> 00:19:59.486 That's correct.
00:19:58.996 --> 00:20:02.295 And even within exact match on that one. So something that we
00:20:02.295 --> 00:20:03.466 did learn is that our.
00:20:04.526 --> 00:20:09.374 However, it is that we've set up the string searching it doesn't
00:20:09.374 --> 00:20:09.896 handle.
00:20:10.846 --> 00:20:13.816 It doesn't do well with spaces. It gets a little weird.
00:20:17.946 --> 00:20:19.216 One moment someone at my door.
00:20:18.216 --> 00:20:20.116 So if I did like.
00:20:21.186 --> 00:20:21.856 Yeah.
00:20:23.756 --> 00:20:25.246 The way that it indexes it.
00:20:26.136 --> 00:20:29.713 It should be each word individually, so I'm not sure
00:20:29.713 --> 00:20:31.806 why spaces are such a big deal.
00:20:35.236 --> 00:20:38.254 Yeah, I'm not sure why either, but we noticed that the suggest
00:20:38.254 --> 00:20:40.888 results become a lot less accurate if your query has a
00:20:40.888 --> 00:20:41.176 space.
00:20:42.446 --> 00:20:46.140 And I'm guessing that it may be a similar thing for the for the
00:20:46.140 --> 00:20:47.006 search as well.
00:20:48.246 --> 00:20:49.116 Let me just a second.
00:20:50.126 --> 00:20:51.076 Yeah, yeah, yeah.
00:20:53.126 --> 00:20:56.146 My name is appended. I guess they just.
00:20:57.126 --> 00:20:58.236 Did that intentionally?
00:21:02.366 --> 00:21:03.046 Yeah, I guess.
00:21:06.816 --> 00:21:08.026 There's the ads carousel.
00:21:09.936 --> 00:21:11.816 Not too mobile responsive.
00:21:14.076 --> 00:21:17.576 If it works, we can make it mobile responsive later.
00:21:17.056 --> 00:21:20.472 Yeah, it works. We need to put some. We need to put some space
00:21:20.472 --> 00:21:23.076 in between the pictures, I think. But you know.
00:21:24.236 --> 00:21:24.996 It does work.
00:21:30.616 --> 00:21:34.596 So I guess for the company name, right, like.
00:21:36.986 --> 00:21:43.172 Can we mix like exact search on this field with fuzzy search on
00:21:43.172 --> 00:21:44.526 this field or?
00:21:48.326 --> 00:21:54.477 Since the keywords so jobber now that's it's a job title. So. So
00:21:54.477 --> 00:21:59.966 yeah. So areas industry job or if we go look at database.
00:22:01.686 --> 00:22:03.356 As your keywords.
00:22:07.676 --> 00:22:10.256 The word keyword is literally being stored.
00:22:15.696 --> 00:22:19.796 I was wondering if job or yeah industry job or store manager.
00:22:20.746 --> 00:22:24.130 It's the job title, but the keyword is industry job or I
00:22:24.130 --> 00:22:26.446 don't know what industry job or means.
00:22:27.636 --> 00:22:31.016 I was looking this one of Ford store manager is not here.
00:22:32.146 --> 00:22:32.936 Wonder if.
00:22:34.976 --> 00:22:36.026 Sorry about that, I'm back.
00:22:35.396 --> 00:22:37.976 And because jobber.
00:22:44.266 --> 00:22:47.434 Areas industry job. So we're searching about job area, but
00:22:47.434 --> 00:22:49.046 that's because they're in the.
00:22:49.866 --> 00:22:51.776 But I think in the.
00:22:52.756 --> 00:22:54.396 As your keywords field.
00:22:55.776 --> 00:22:56.846 So like pain.
00:22:59.926 --> 00:23:02.256 So I think I don't know if I have any painters.
00:23:04.566 --> 00:23:06.636 Tell her prepper clears tag.
00:23:08.796 --> 00:23:12.406 Presented manager makes her straight and look for one that
00:23:12.406 --> 00:23:13.446 had like similar.
00:23:15.836 --> 00:23:21.246 Can it show Carson's pregnant pregnant company, Maine?
00:23:23.116 --> 00:23:23.476 The.
00:23:26.736 --> 00:23:29.996 So it it does seem that it is searching on.
00:23:31.736 --> 00:23:36.266 Keywords, job title or company. It's just not like.
00:23:41.666 --> 00:23:45.616 Not exact right, so maybe I spelled deluxe wrong.
00:23:53.766 --> 00:23:56.236 See Premium company name.
00:23:57.126 --> 00:24:01.540 Is a job company name. There's premium company. It doesn't come
00:24:01.540 --> 00:24:04.576 up, but premium company name is right here.
00:24:05.846 --> 00:24:07.806 So if I search premium company.
00:24:08.736 --> 00:24:10.286 Neither of those come up.
00:24:13.596 --> 00:24:13.916 Umm.
00:24:32.156 --> 00:24:32.576 That's good.
00:24:33.826 --> 00:24:34.896 That's testing.
00:24:36.256 --> 00:24:36.706 To.
00:24:43.096 --> 00:24:44.296 None for test.
00:24:47.606 --> 00:24:48.036 But.
00:24:54.216 --> 00:24:55.326 Yeah, it's just not.
00:24:58.666 --> 00:25:00.456 Not very reliable.
00:25:03.046 --> 00:25:05.506 See like test and test 2.
00:25:06.276 --> 00:25:07.546 Those are company names.
00:25:29.166 --> 00:25:29.486 Yeah.
00:25:34.966 --> 00:25:36.496 Any thoughts?
00:25:39.056 --> 00:25:43.812 Let's go look at the the indexer for the jobs and the search
00:25:43.812 --> 00:25:47.166 module. Again. Let's start at the indexer.
00:25:48.476 --> 00:25:48.706 OK.
00:25:50.726 --> 00:25:52.076 Scroll down a little bit.
00:25:54.296 --> 00:25:57.130 That's something to look at right there. That map method
00:25:57.130 --> 00:25:57.976 that has all the.
00:25:58.736 --> 00:25:59.746 Properties and stuff.
00:26:11.606 --> 00:26:11.966 OK.
00:26:12.696 --> 00:26:13.626 And I'll looks.
00:26:17.136 --> 00:26:18.186 And all looks good.
00:26:29.016 --> 00:26:32.226 So we have a look at it again, sorry one more time.
00:26:31.136 --> 00:26:32.256 Then you said.
00:26:35.776 --> 00:26:37.226 OK, scroll to the right.
00:26:38.606 --> 00:26:39.806 So we have name.
00:26:40.806 --> 00:26:43.026 Analyze by analyzer for product name.
00:26:43.636 --> 00:26:44.856 And then fields.
00:26:45.506 --> 00:26:50.068 They have a text field name, keyword analyzer, product name
00:26:50.068 --> 00:26:52.426 for keyword and the keyword is.
00:26:53.646 --> 00:26:55.756 Name raw.
00:26:58.076 --> 00:26:58.506 Hmm.
00:27:25.876 --> 00:27:30.316 Yeah. See this because copy track the product indexer.
00:27:31.586 --> 00:27:33.386 Yeah, almost definitely.
00:27:34.356 --> 00:27:34.636 It's.
00:27:38.376 --> 00:27:41.611 And it doesn't have any of these nested this right, which
00:27:41.611 --> 00:27:43.006 probably aren't required.
00:27:43.536 --> 00:27:45.976 Yeah, we don't have any nested data structures on this.
00:27:46.996 --> 00:27:47.406 OK.
00:27:49.536 --> 00:27:51.566 Conversation that's for the text I had.
00:27:50.396 --> 00:27:53.306 I don't care. That's the. Yeah, that's for the suggestions.
00:27:53.306 --> 00:27:56.362 Yeah. So let's look at something like the product name and and
00:27:53.956 --> 00:27:54.496 Yeah.
00:27:56.362 --> 00:27:57.526 see if they're the same.
00:28:02.696 --> 00:28:03.926 Like look at this one.
00:28:04.566 --> 00:28:05.086 Yeah.
00:28:06.076 --> 00:28:07.816 They look like they're exactly the same.
00:28:06.306 --> 00:28:10.879 Yeah, it looks like analyzer. Yeah. Fields text on keyword
00:28:10.879 --> 00:28:15.996 analyzer, front keyword, keyword name wrong that looks identical.
00:28:16.856 --> 00:28:17.276 Yeah.
00:28:20.936 --> 00:28:21.416 Hmm.
00:28:31.896 --> 00:28:34.785 Like you heard, how much question Mark you heard Nate,
00:28:34.785 --> 00:28:35.416 that's yeah.
00:28:51.336 --> 00:28:55.996 And so that like test test to those would be company name.
00:28:57.556 --> 00:28:59.546 The fuzziness is set to auto.
00:29:02.616 --> 00:29:04.026 Is it the same in the UM?
00:29:03.326 --> 00:29:04.156 I don't know what.
00:29:06.196 --> 00:29:07.566 Also wait, what was the?
00:29:08.666 --> 00:29:13.101 Uh, that suffix keyword that suffix keyword dot suffix
00:29:13.101 --> 00:29:13.746 keyword.
00:29:15.436 --> 00:29:15.856 Hmm.
00:29:18.086 --> 00:29:21.788 I wonder if any of these should be instead of suffix keyword.
00:29:21.788 --> 00:29:24.536 They should be like suffix name or something.
00:29:25.876 --> 00:29:29.046 Like this one means like suffix company name or suffix.
00:29:28.806 --> 00:29:31.706 Let's look at like the product search.
00:29:36.096 --> 00:29:38.746 Yeah. And compare that to what we're looking at for hours.
00:29:40.566 --> 00:29:43.770 Let's expand like match screw back up. There's like a match in
00:29:43.770 --> 00:29:46.416 prefix by name collapse region. Yeah, look at that.
00:29:47.446 --> 00:29:49.076 So that's just keyword too.
00:29:55.356 --> 00:29:57.676 Referring valley query.
00:30:00.316 --> 00:30:02.046 That's all the same.
00:30:04.226 --> 00:30:07.936 Free experience this one it says keyword as well yeah.
00:30:10.766 --> 00:30:15.016 Name dot keyword or name dot suffix in the past keyword.
00:30:17.076 --> 00:30:18.426 So cute word.
00:30:19.296 --> 00:30:21.296 Look on that keyword variable and F-12.
00:30:23.306 --> 00:30:25.889 Ohh never mind, I saw it in the thing. It's just the word
00:30:25.889 --> 00:30:26.246 keyword.
00:30:26.896 --> 00:30:27.466 Yeah.
00:30:30.256 --> 00:30:30.526 Hmm.
00:30:31.716 --> 00:30:33.006 That's curious, isn't it?
00:30:34.036 --> 00:30:35.986 I guess it just cause it's used in a lot of places.
00:30:37.386 --> 00:30:41.694 Yeah, I mean not not the not the static string, right? But like
00:30:41.694 --> 00:30:44.926 the they're just passing it the string keyword.
00:30:46.706 --> 00:30:48.016 For the suffix like.
00:30:47.196 --> 00:30:49.146 So that's also used in the indexer.
00:30:52.286 --> 00:30:52.726 Yeah.
00:30:56.356 --> 00:30:58.136 Maybe that's the stream?
00:30:58.826 --> 00:30:59.376 Keeper.
00:31:06.606 --> 00:31:06.906 Click.
00:31:11.246 --> 00:31:13.246 I've messed stuff that we don't need to worry about.
00:31:22.056 --> 00:31:27.043 So remember, I told you that I couldn't get my catalog. The job
00:31:27.043 --> 00:31:32.186 opening catalog to load unless I had the job resume search index.
00:31:34.606 --> 00:31:35.256 Yeah, I remember that.
00:31:34.766 --> 00:31:35.246 Uh.
00:31:37.716 --> 00:31:40.007 You think that affects anything has anything to do with
00:31:40.007 --> 00:31:40.376 anything.
00:31:40.986 --> 00:31:43.899 It shouldn't affect the results coming back. It's probably just
00:31:41.296 --> 00:31:41.746 Because.
00:31:43.899 --> 00:31:46.857 some weird logic somewhere that makes them depend on each other,
00:31:46.857 --> 00:31:49.452 but the results coming back should all be through what's
00:31:49.452 --> 00:31:52.137 being indexed, how it's being analyzed, and how it's being
00:31:52.137 --> 00:31:55.096 queried. And those are the three files that you have open there.
00:31:53.506 --> 00:31:53.836 OK.
00:31:55.886 --> 00:32:02.165 Yeah. So did we need to reindex the jobs after modifying any of
00:32:02.165 --> 00:32:02.656 this?
00:32:03.636 --> 00:32:05.286 Uh couldn't hurt.
00:32:07.446 --> 00:32:10.116 I don't. I don't think that that would be.
00:32:19.246 --> 00:32:21.376 Probably not anything to do with like.
00:32:21.886 --> 00:32:22.296 Yeah.
00:32:23.936 --> 00:32:26.564 Why it's matching on some and not matching on the others,
00:32:26.564 --> 00:32:26.836 right?
00:32:27.156 --> 00:32:28.166 Yeah, yeah.
00:32:29.306 --> 00:32:31.306 Since all we changed in the indexer was the.
00:32:32.086 --> 00:32:33.436 Location related stuff.
00:32:32.656 --> 00:32:33.016 Yeah.
00:32:34.336 --> 00:32:36.602 Yeah, I don't know why this loading symbol is still
00:32:36.602 --> 00:32:38.346 spinning. It's doing it the whole time.
00:32:40.416 --> 00:32:43.546 Uh, I don't know if it's. I'll tell that's about.
00:32:54.826 --> 00:32:55.556 Working pending.
00:32:58.346 --> 00:32:59.126 Well, that's stupid.
00:33:01.896 --> 00:33:07.168 Let's try so the ZIP code search is enabled in the index room
00:33:07.168 --> 00:33:12.610 module stuff. Would it? Do you think it would work at all if we
00:33:12.610 --> 00:33:14.226 tried to pass in a?
00:33:17.426 --> 00:33:18.136 Zip code.
00:33:23.046 --> 00:33:23.936 Probably not.
00:33:24.126 --> 00:33:26.915 It wouldn't filter by the ZIP code if you typed it into the
00:33:26.915 --> 00:33:28.496 search bar, but when you go into.
00:33:29.256 --> 00:33:30.846 The catalog there.
00:33:33.476 --> 00:33:34.536 Yeah, right there.
00:33:35.156 --> 00:33:39.807 So for this the way it's set up. Thank you have to enter a job
00:33:39.807 --> 00:33:41.136 area, a job title.
00:33:41.836 --> 00:33:45.321 Click search and then filter those search results based on a
00:33:45.321 --> 00:33:45.836 ZIP code.
00:33:46.426 --> 00:33:49.456 So you can't search with just having.
00:33:50.976 --> 00:33:53.565 Everything else, because that would, that's just bad form
00:33:53.565 --> 00:33:56.287 validation or something on the front end. Yeah, that you you
00:33:56.287 --> 00:33:59.144 don't need to have a position to filter by like there's nothing
00:33:59.144 --> 00:34:01.822 in the lastic or in the rest of the code that would enforce
00:34:01.822 --> 00:34:02.626 that. That's just.
00:34:03.716 --> 00:34:05.786 Some weird form validation or something going on?
00:34:06.746 --> 00:34:07.106 OK.
00:34:07.286 --> 00:34:09.566 You shouldn't need to choose a job position.
00:34:10.316 --> 00:34:13.089 To filter by jobs in an area that doesn't really make any
00:34:13.089 --> 00:34:13.376 sense.
00:34:14.856 --> 00:34:15.186 Yeah.
00:34:16.066 --> 00:34:18.945 And I would. I would be shocked if that's what the client was
00:34:18.945 --> 00:34:19.456 asking for.
00:34:20.076 --> 00:34:23.527 They're not for sure. This is. I got a ticket to fix this. That's
00:34:23.527 --> 00:34:26.875 what I was wondering if it was anything to do with, like, if if
00:34:26.875 --> 00:34:29.176 this was implemented this way for a reason.
00:34:40.056 --> 00:34:44.826 So like location Carlsbad 90029, the way it stands now, I can't
00:34:44.826 --> 00:34:49.447 search that without searching something to get this to pop up
00:34:49.447 --> 00:34:52.056 and then filtering it by Carlsbad.
00:34:53.606 --> 00:34:55.256 I might be able to do the city search.
00:34:57.776 --> 00:35:00.456 Yeah, I can search by yeah, city.
00:35:03.046 --> 00:35:05.776 Just not the ZIP code and distance from. I don't know why.
00:35:05.616 --> 00:35:09.158 Yeah, I'm. I don't understand why that would even have a
00:35:09.158 --> 00:35:13.073 choose a position first. Like I I'm not. I'm not sure. I could
00:35:13.073 --> 00:35:14.876 even guess why that was done.
00:35:18.256 --> 00:35:20.630 Yeah. See, that makes it look like it's real intentional,
00:35:20.630 --> 00:35:20.876 right?
00:35:21.246 --> 00:35:23.066 As this definitely intentional.
00:35:23.776 --> 00:35:26.146 Let's just get rid of that on the front end then.
00:35:29.926 --> 00:35:32.936 And then a catalog job catalog.
00:35:34.496 --> 00:35:36.746 Are going to be in the catalog filters I think.
00:35:35.176 --> 00:35:39.756 Ohh yeah, filters. Yeah so scared that.
00:35:43.716 --> 00:35:44.596 Catalog.
00:35:46.596 --> 00:35:48.426 It's kinda like filter components.
00:35:49.146 --> 00:35:50.306 Draw position.
00:35:49.376 --> 00:35:52.989 I think it's, yeah, it could be. Uh, distance filter. It could be
00:35:52.989 --> 00:35:55.836 in job catalog filters itself. Uh, yeah, there's a.
00:35:57.096 --> 00:35:59.326 I guess not. Add control F on this page for that.
00:36:00.016 --> 00:36:01.896 That string of whatever that was.
00:36:04.286 --> 00:36:05.576 Ohh yeah.
00:36:06.596 --> 00:36:07.046 Us.
00:36:07.926 --> 00:36:08.776 Choose.
00:36:09.736 --> 00:36:10.706 Ohh, parking.
00:36:13.676 --> 00:36:15.026 I have to look at it, please.
00:36:16.836 --> 00:36:18.236 Choose a position first.
00:36:19.216 --> 00:36:21.036 OK, that's fine. That in the code.
00:36:24.406 --> 00:36:25.136 Yeah, here.
00:36:24.436 --> 00:36:27.486 There it is, if not query.
00:36:28.236 --> 00:36:30.196 And then render that OK.
00:36:30.886 --> 00:36:34.296 So delete that line.
00:36:40.546 --> 00:36:44.035 OK. And then figure out where else it's trying to enforce
00:36:44.035 --> 00:36:44.336 that?
00:36:45.946 --> 00:36:49.672 Hmm, disabled equals form states valid or not query remove or not
00:36:46.686 --> 00:36:47.896 An added distance.
00:36:49.672 --> 00:36:50.576 query from that.
00:36:53.446 --> 00:36:55.286 Yeah, OK, save.
00:36:57.426 --> 00:36:58.266 And.
00:37:00.066 --> 00:37:00.716 Yeah, that works.
00:37:49.916 --> 00:37:53.206 Yeah. And then like I had a a QA fail ticket.
00:37:54.386 --> 00:37:58.910 Based on following that like format of searching for tech
00:37:58.910 --> 00:38:03.435 representative 1st and then entering a ZIP code from that
00:38:03.435 --> 00:38:06.166 job posting and no search results.
00:38:10.876 --> 00:38:12.456 So I don't know what.
00:38:13.656 --> 00:38:16.626 Why? Why? All that is why it is?
00:38:24.396 --> 00:38:26.306 Now we should just be able to say.
00:38:27.486 --> 00:38:29.616 06820.
00:38:30.176 --> 00:38:33.286 Ohh, within a distance of 100 miles.
00:38:35.546 --> 00:38:38.416 068206854.
00:38:39.786 --> 00:38:40.476 Like uh.
00:38:43.376 --> 00:38:44.136 It's like that worked.
00:38:45.836 --> 00:38:48.164 Yeah, I mean, I don't know the mileage right, like, I don't
00:38:48.164 --> 00:38:49.406 know if the mileage is accurate.
00:38:50.686 --> 00:38:52.206 Because both of these pop up with it.
00:38:50.986 --> 00:38:56.451 Yeah, I don't know how far away 6820 is from 6854. Let's consult
00:38:56.326 --> 00:38:57.076 Yeah.
00:38:56.451 --> 00:38:57.376 the Oracle.
00:38:58.236 --> 00:38:59.586 Yeah, there you go.
00:39:00.536 --> 00:39:03.809 Ask Google Maps. See how close together those are just to make
00:39:03.809 --> 00:39:05.056 sure that it's not like.
00:39:06.296 --> 00:39:08.704 Like, make sure that that distance number is being passed
00:39:08.704 --> 00:39:10.116 through correctly and everything.
00:39:11.096 --> 00:39:12.876 Let's see 06820.
00:39:18.246 --> 00:39:20.336 And then obviously it's 854.
00:39:22.166 --> 00:39:23.666 Probably relatively close.
00:39:23.836 --> 00:39:26.868 Oh yeah, they're like 5 miles from each other, if even that.
00:39:26.266 --> 00:39:28.676 OK. Yeah, so that works.
00:39:26.868 --> 00:39:29.106 Like one or two miles. So that's fine. Yeah.
00:39:29.706 --> 00:39:30.126 Yeah.
00:39:32.646 --> 00:39:33.056 Cool.
00:39:32.856 --> 00:39:35.026 So it caught it in all three of those.
00:39:37.356 --> 00:39:38.416 Yeah, which makes sense.
00:39:38.266 --> 00:39:39.266 Yeah, yeah.
00:39:40.426 --> 00:39:42.566 So that's working right as far as that's concerned.
00:39:47.046 --> 00:39:47.776 Ohly.
00:39:50.356 --> 00:39:51.196 We do that.
00:39:53.616 --> 00:39:56.936 33039 and not clear that it's here.
00:39:56.856 --> 00:39:59.689 Looked like it got rid of your distance filter when you did
00:39:59.689 --> 00:39:59.926 that.
00:40:01.746 --> 00:40:03.016 Which is a little confusing.
00:40:01.796 --> 00:40:02.836 Ohh.
00:40:04.236 --> 00:40:05.046 So.
00:40:04.496 --> 00:40:07.911 It's like so if you if you select a distance filter and
00:40:07.911 --> 00:40:10.656 then select a job area and and or job title.
00:40:11.986 --> 00:40:16.277 It it it's just 6820 and then 100 miles. Yeah, whatever. It
00:40:16.277 --> 00:40:20.568 doesn't matter. Add distance. OK, so it added the distance,
00:40:20.568 --> 00:40:21.856 but it didn't. Oh.
00:40:24.406 --> 00:40:26.256 It didn't add it in the.
00:40:27.826 --> 00:40:30.296 Umm the query string in the URL?
00:40:33.026 --> 00:40:33.466 Umm.
00:40:34.586 --> 00:40:38.544 But whenever you change the job area on job title, does it do it
00:40:38.544 --> 00:40:42.320 there? Because if not then a lot of catalog stuff is going to
00:40:42.320 --> 00:40:44.756 need a lot of work. So hit add OK yeah.
00:40:45.936 --> 00:40:48.646 I just did and term equals other, OK.
00:40:50.976 --> 00:40:51.686 That's weird.
00:40:52.646 --> 00:40:56.583 So let me let me get rid of that and let me say I don't know,
00:40:56.583 --> 00:40:57.536 we're mixer is.
00:40:58.946 --> 00:41:00.246 Probably shop floor.
00:41:04.006 --> 00:41:04.636 There it is.
00:41:06.856 --> 00:41:09.106 Ah, it did clear the filter again.
00:41:15.286 --> 00:41:17.656 So that works. I don't know why it's clear on the filter.
00:41:21.316 --> 00:41:25.303 I think it's clearing it because it's not in the, it's not
00:41:24.996 --> 00:41:25.556 You arial.
00:41:25.303 --> 00:41:29.628 setting it in the right place. Yeah, and the the URL is what it
00:41:29.628 --> 00:41:33.142 gets partially used as. Basically the state for the
00:41:33.142 --> 00:41:37.331 search form. That way you can link someone to a specific page
00:41:37.331 --> 00:41:41.116 of results with a specific filter and sort and whatnot.
00:41:50.216 --> 00:41:51.326 Spanish.
00:42:25.326 --> 00:42:26.396 009.
00:42:28.346 --> 00:42:29.566 This is Houston.
00:42:30.896 --> 00:42:33.686 Oh, I don't know about that. I don't know about the names.
00:42:34.826 --> 00:42:35.666 Arkansas.
00:42:36.626 --> 00:42:40.309 That's OK. Right now, it's Alaska sheets in Alaska. Yeah,
00:42:38.656 --> 00:42:40.896 That's Alaska. Yeah, Arkansas, AR.
00:42:40.309 --> 00:42:44.056 that's not. Yeah, that's not real. But this might be real.
00:42:42.526 --> 00:42:47.522 Houston, Alaska. 89, double 091. Let's see if that's an actual
00:42:47.522 --> 00:42:48.236 ZIP code.
00:42:49.546 --> 00:42:52.536 Yeah, the the city's not real, but the ZIP code.
00:42:51.976 --> 00:42:54.706 Yeah, definitely not. Yeah, we don't care about the.
00:42:57.176 --> 00:43:01.611 OK, well the ZIP code for that is in fact in Nevada. It's
00:43:01.611 --> 00:43:03.906 Henderson, NV, Nevada, Nevada.
00:43:02.966 --> 00:43:07.986 OK. And then that might be within 20 miles of Carlsbad, CA.
00:43:10.036 --> 00:43:13.766 Which I don't know if that City's right, but that 92009.
00:43:18.846 --> 00:43:19.146 Oops.
00:43:19.516 --> 00:43:20.706 99.
00:43:22.286 --> 00:43:25.910 That does indeed correspond to Carlsbad, but those two places
00:43:25.910 --> 00:43:27.956 are definitely not 20 miles apart.
00:43:29.746 --> 00:43:30.976 Yeah, ohhh wait.
00:43:32.026 --> 00:43:32.426 Uh.
00:43:33.636 --> 00:43:34.186 That's why.
00:43:35.286 --> 00:43:40.164 It didn't it the distance filter wasn't applied fees. OK. Yeah. I
00:43:39.176 --> 00:43:43.566 Ah, OK. Gonna say those places are roughly 250 miles.
00:43:40.164 --> 00:43:44.747 don't know if I didn't hit add distance. Yeah, yeah, yeah. So
00:43:44.747 --> 00:43:49.033 that looks like it's it's working for the most part every
00:43:44.896 --> 00:43:45.326 OK.
00:43:49.033 --> 00:43:52.286 now and then it's it's clearing the filter.
00:43:51.896 --> 00:43:55.577 Yeah. And the the the clearing filters is definitely there's a
00:43:55.577 --> 00:43:59.433 front end issue with the way the catalog is accepting that filter
00:43:59.433 --> 00:44:01.946 data. It's not putting it on to the right.
00:44:02.786 --> 00:44:06.206 It's not storing it in the right place. Something else is making
00:44:06.206 --> 00:44:09.520 that query call or something's been changed about the way that
00:44:09.520 --> 00:44:12.835 query call works, that it's not storing the the state into the
00:44:12.835 --> 00:44:15.939 query string the way that it's supposed to. And that would
00:44:15.939 --> 00:44:18.938 definitely be a regression from core, because that stuff
00:44:18.938 --> 00:44:22.200 definitely works in core. So if we are, if you're not able to
00:44:22.200 --> 00:44:25.410 figure out why it's not doing that, I would just compare the
00:44:25.410 --> 00:44:28.777 catalog files to the one that's in core specifically looking at
00:44:28.777 --> 00:44:31.671 the section that handles the query, string updates and
00:44:31.671 --> 00:44:33.986 whatnot, and then see if we can figure out.
00:44:36.116 --> 00:44:36.616 OK.
00:44:37.096 --> 00:44:38.036 What broke?
00:44:39.566 --> 00:44:40.716 Look for two in.
00:44:39.726 --> 00:44:40.676 But for now?
00:44:41.446 --> 00:44:44.711 For now, let's not worry about that part. Let's look more at
00:44:44.711 --> 00:44:44.926 the.
00:44:45.966 --> 00:44:49.616 The search results being less less than stellar.
00:44:53.606 --> 00:44:57.446 See Darion, but there are two jobs in location Darien.
00:45:00.606 --> 00:45:01.366 Darien.
00:45:05.386 --> 00:45:05.976 Darian.
00:45:07.736 --> 00:45:10.766 OK. And are they both? They both have the?
00:45:12.796 --> 00:45:16.388 Yeah, they both show the location. OK, so you may need to
00:45:15.486 --> 00:45:16.816 06820.
00:45:16.388 --> 00:45:20.228 also look at how that that city filters doing what it's doing
00:45:20.228 --> 00:45:22.396 because that's probably wrong too.
00:45:24.306 --> 00:45:24.786 OK.
00:45:27.646 --> 00:45:28.306 So.
00:45:31.336 --> 00:45:35.396 That is in the front end, right? It's all in the front end.
00:45:37.686 --> 00:45:40.535 Uh, it should be sending the city to the back end and
00:45:40.535 --> 00:45:43.860 receiving the filtered data from the back end. It shouldn't be
00:45:43.860 --> 00:45:45.496 doing any filtering on its own.
00:45:46.626 --> 00:45:48.386 OK, where are the filters?
00:45:46.806 --> 00:45:47.796 If it is.
00:45:48.876 --> 00:45:51.901 That's all going to be in the search module and the indexer
00:45:51.901 --> 00:45:52.406 and stuff.
00:45:54.506 --> 00:45:54.836 OK.
00:45:55.946 --> 00:45:59.804 Anything that drives which items come back in the results is
00:45:59.804 --> 00:46:00.816 gonna be in the.
00:46:01.556 --> 00:46:06.146 Uh elastic search provider in the catalog.
00:46:07.486 --> 00:46:11.123 Obviously, if you're like direct querying from the database or
00:46:11.123 --> 00:46:14.587 anything like that, then it could be a workflow or it could
00:46:14.587 --> 00:46:18.339 be the filtering project in the data model layer. But if it's if
00:46:18.339 --> 00:46:21.283 it's catalog related specifically with any catalog
00:46:21.283 --> 00:46:24.343 filters and then determining which results should be
00:46:24.343 --> 00:46:27.576 displayed, that's always going to be the elastic search
00:46:27.576 --> 00:46:28.096 provider.
00:46:29.196 --> 00:46:29.886 Umm.
00:46:29.446 --> 00:46:29.826 OK.
00:46:30.996 --> 00:46:34.655 And that's all that the elastic search provider does. It only
00:46:34.655 --> 00:46:38.314 determines what things, what products or what job openings or
00:46:38.314 --> 00:46:41.737 whatever should display. It doesn't handle what data gets
00:46:41.737 --> 00:46:44.216 displayed for them. So if you're editing.
00:46:45.006 --> 00:46:48.756 Uh, you're editing like images for a product or something like
00:46:48.756 --> 00:46:52.268 that. You don't need to reindex the catalog because images
00:46:52.268 --> 00:46:55.840 images are not part of the index. And yeah, and and even if
00:46:53.716 --> 00:46:54.966 Indexed, yeah.
00:46:55.840 --> 00:46:56.436 they were.
00:46:57.126 --> 00:47:00.454 The index doesn't doesn't dictate what actually gets
00:47:00.454 --> 00:47:04.411 rendered on a product card. It just determines what product to
00:47:04.411 --> 00:47:08.305 display for that card and we we then load the name and custom
00:47:08.305 --> 00:47:12.199 key directly from the database and not from the Elasticsearch
00:47:12.199 --> 00:47:12.576 index.
00:47:13.586 --> 00:47:14.136 Umm.
00:47:14.046 --> 00:47:18.109 So it looks like on the indictable model that we are
00:47:18.109 --> 00:47:19.106 indexing the.
00:47:19.806 --> 00:47:21.436 And we a property.
00:47:22.826 --> 00:47:24.066 Contact city.
00:47:24.876 --> 00:47:27.776 Is this what is being used for the city filter?
00:47:28.036 --> 00:47:31.718 Probably click on that contact City right there and then scroll
00:47:31.718 --> 00:47:35.113 up. Uh, yeah, that one right there. And then scroll up and
00:47:35.113 --> 00:47:35.286 OK.
00:47:35.986 --> 00:47:39.764 Contact address city. Alright, cool. That makes sense. That's
00:47:36.656 --> 00:47:38.036 That's coming off the address.
00:47:39.764 --> 00:47:42.446 fine. OK, so let's go to the search module.
00:47:41.586 --> 00:47:41.876 Yeah.
00:47:43.696 --> 00:47:48.456 Let's see what's going on. Cities, single query
00:47:48.456 --> 00:47:49.746 modification.
00:47:56.516 --> 00:48:01.043 OK, so we already know that the city like we are successfully
00:48:01.043 --> 00:48:05.498 passing it in and then it's returned query and equals plus Q
00:48:05.498 --> 00:48:08.346 love that syntax not confusing at all.
00:48:09.286 --> 00:48:09.946 Umm.
00:48:11.266 --> 00:48:16.729 A bull. The name is nested name for record City. Single boost by
00:48:16.729 --> 00:48:17.906 the city term.
00:48:18.726 --> 00:48:19.686 Should.
00:48:23.306 --> 00:48:25.836 I don't know that we need a minimum should match on that.
00:48:29.416 --> 00:48:29.756 Sure.
00:48:30.976 --> 00:48:32.956 Move this or content comment it out.
00:48:37.386 --> 00:48:41.166 Mouse over that minimum should match part and see what it says
00:48:41.166 --> 00:48:44.226 like to the left of that. Like the function, yeah.
00:48:48.606 --> 00:48:51.594 That's member number of the optional Boolean clauses which
00:48:51.594 --> 00:48:52.506 must be satisfied.
00:48:54.276 --> 00:48:55.946 So OK, I guess that's fine.
00:48:56.756 --> 00:48:57.916 Because there's only one.
00:48:59.626 --> 00:49:00.536 Uh bullying?
00:48:59.876 --> 00:49:02.246 Yeah, it's it's basically saying.
00:49:03.136 --> 00:49:03.876 Umm.
00:49:05.536 --> 00:49:08.846 That this Boolean has a should, but that it that it.
00:49:09.326 --> 00:49:12.079 Umm, it has to match, which I think then you would just
00:49:12.079 --> 00:49:15.079 change. You should to a match rather than doing a should and
00:49:15.079 --> 00:49:16.456 then a minimum should match.
00:49:18.676 --> 00:49:21.376 But I don't know elastic is confusing.
00:49:22.456 --> 00:49:27.304 Yeah. So can you add multiple shirts here? And like minimum
00:49:26.956 --> 00:49:27.546 Yes.
00:49:27.304 --> 00:49:32.314 should match fix to one. So we have a minimum of should match
00:49:32.314 --> 00:49:33.446 on one of the.
00:49:34.206 --> 00:49:34.536 Yeah.
00:49:34.236 --> 00:49:36.686 Fields, but we could have like five shots.
00:49:37.066 --> 00:49:40.133 Yeah, you could have five of them, and if and then that
00:49:40.133 --> 00:49:43.638 minimum should match. Would be if any one of them matches, then
00:49:43.638 --> 00:49:47.143 the Boolean would be true. Then this this filter would be true.
00:49:46.026 --> 00:49:46.376 Umm.
00:49:47.143 --> 00:49:50.539 Or you could have it require a minimum match of two, and then
00:49:50.539 --> 00:49:53.880 you'd have to have two out of the five filters that actually
00:49:53.880 --> 00:49:56.016 goes through for that Boolean to pass.
00:49:56.886 --> 00:49:57.286 OK.
00:50:00.566 --> 00:50:02.436 And we returned the query, so I mean.
00:50:22.916 --> 00:50:23.406 We think.
00:50:26.316 --> 00:50:27.446 This is probably fine.
00:50:28.206 --> 00:50:33.256 UM, we may have something wrong with the. What we could do is.
00:50:34.576 --> 00:50:39.892 We could add a dot trim to form dot city and then .2 lower on it
00:50:39.892 --> 00:50:41.446 as well on line 47.
00:50:42.936 --> 00:50:47.147 Form dot city dot trim tolower. Ohh you're off by off by one on
00:50:47.147 --> 00:50:48.726 that. Yeah there you go.
00:50:52.006 --> 00:50:53.276 And then at 2 lower.
00:50:55.506 --> 00:50:58.568 And then exclamation point after cities. So you already confirmed
00:50:58.568 --> 00:50:59.636 it's not null up there.
00:51:03.526 --> 00:51:06.406 Alright, cool. And then let's do the same.
00:51:08.826 --> 00:51:11.510 Ohh, I'd into the closing parenthesis to the end of the
00:51:11.510 --> 00:51:12.756 line. Before that I think.
00:51:14.876 --> 00:51:15.626 Yeah, there you go.
00:51:16.636 --> 00:51:18.126 Uh, OK. Saves there.
00:51:20.226 --> 00:51:22.216 Alright, let's go into search module.
00:51:24.296 --> 00:51:25.326 Or sorry dump reader.
00:51:26.776 --> 00:51:31.246 And let's go ahead and add a a Scroll down a little bit.
00:51:34.206 --> 00:51:38.351 Contact City right there at the end of that line. Do question
00:51:38.351 --> 00:51:42.296 Mark .2 lower or dot question mark dot trim dot too lower.
00:51:50.146 --> 00:51:51.036 Yeah, cool.
00:51:52.616 --> 00:51:57.699 That way, uh, we're storing the city with no leading spaces or
00:51:57.699 --> 00:52:01.975 anything, just in case the data is wonky and with no
00:52:01.975 --> 00:52:03.186 capitalization.
00:52:08.526 --> 00:52:11.182 And then rebuilding the searching providers project
00:52:11.182 --> 00:52:12.306 should be good, right?
00:52:12.866 --> 00:52:16.375 Not a rebuild. So since you did a rebuild, you probably have to
00:52:16.375 --> 00:52:19.500 rebuild the full solution. You'll when you make edits in
00:52:17.396 --> 00:52:17.706 Umm.
00:52:19.500 --> 00:52:22.736 that provider. Certain providers you can do a build on the
00:52:22.736 --> 00:52:25.861 provider itself, not a rebuild, but since you're doing a
00:52:25.166 --> 00:52:25.916 OK.
00:52:25.861 --> 00:52:27.616 rebuild, it's probably going to.
00:52:28.686 --> 00:52:31.316 Get a little weird and.
00:52:30.776 --> 00:52:31.166 OK.
00:52:32.346 --> 00:52:32.746 Yeah.
00:52:32.886 --> 00:52:34.596 Throughout some DLL's or something?
00:52:36.326 --> 00:52:37.356 Probably.
00:53:12.166 --> 00:53:13.786 Some great experimenter.
00:53:48.776 --> 00:53:50.446 Split on space.
00:53:51.596 --> 00:53:52.616 That's really.
00:53:54.996 --> 00:53:55.596 Search.
00:53:56.306 --> 00:53:57.236 Regex.
00:54:05.996 --> 00:54:08.106 Going to join it back? Clean space.
00:54:13.766 --> 00:54:14.726 Listening. That's right.
00:54:30.026 --> 00:54:31.896 You've got sharing violations in the.
00:54:32.826 --> 00:54:34.706 Long, yeah, pulls might still be on.
00:54:36.646 --> 00:54:37.326 To ease.
00:54:40.526 --> 00:54:40.976 And.
00:54:43.806 --> 00:54:44.556 So like.
00:54:45.826 --> 00:54:47.106 New here or something?
00:54:48.406 --> 00:54:49.256 Ohh I'm doing.
00:54:48.626 --> 00:54:49.196 All good.
00:54:52.366 --> 00:54:55.910 I still, I still make that make that mistake every now and then
00:54:55.910 --> 00:54:56.076 so.
00:54:58.106 --> 00:54:59.156 It's one of those things that.
00:54:59.926 --> 00:55:01.126 Just never goes away.
00:55:03.176 --> 00:55:05.156 It just it just happens less frequently.
00:55:11.466 --> 00:55:13.186 Browse through the tickets concerning.
00:55:13.906 --> 00:55:18.096 Search filtering, that sort of thing and see.
00:55:32.256 --> 00:55:36.353 See Sykes search should not be case sensitive. I have a bug
00:55:36.353 --> 00:55:37.446 ticket for that.
00:55:39.106 --> 00:55:40.006 That's what he says.
00:55:51.066 --> 00:55:56.206 Tech represent tentative no search, no stuff found.
00:55:56.716 --> 00:55:59.846 Profit was failed status 401.
00:56:01.666 --> 00:56:04.279 Now that that four one is irrelevant, that's just a load.
00:56:04.279 --> 00:56:05.946 The current wallet and current user.
00:56:06.636 --> 00:56:07.156 OK.
00:56:12.386 --> 00:56:14.916 I'm yeah. OK. Current user, yeah.
00:56:16.266 --> 00:56:19.957 So yeah, there's tech representatives, but lower case
00:56:19.957 --> 00:56:23.853 I guess didn't catch it. It looked like a lower case was
00:56:23.853 --> 00:56:28.092 working, maybe not for all of them though, might be the space
00:56:28.092 --> 00:56:29.596 thing throwing it off.
00:56:37.546 --> 00:56:39.656 Good, Lee.
00:56:41.236 --> 00:56:41.686 What?
00:56:42.716 --> 00:56:45.796 Error. Did you see that? Let you know that?
00:56:44.706 --> 00:56:50.131 I am seeing I am seeing that I just noticed this name, version
00:56:50.131 --> 00:56:55.728 name. Replace the job title and the name space is being replaced
00:56:55.728 --> 00:56:57.106 with percent 20.
00:56:58.956 --> 00:57:00.646 Yeah, this fails all the time.
00:56:59.306 --> 00:57:00.266 I didn't even notice it.
00:57:02.066 --> 00:57:05.816 This fails in the network call. You'll see it say, uh, job.
00:57:07.056 --> 00:57:10.506 Job opening Pursuit money failed.
00:57:11.256 --> 00:57:12.086 A network call.
00:57:12.956 --> 00:57:13.286 Huh.
00:57:14.856 --> 00:57:16.216 I'll show you here in just a second.
00:57:14.936 --> 00:57:19.240 OK, let's let's uh, once the build is done, is it done
00:57:19.240 --> 00:57:19.866 already?
00:57:20.556 --> 00:57:21.856 It is the yes.
00:57:22.076 --> 00:57:24.246 OK, remove those replaces.
00:57:26.026 --> 00:57:26.696 On both.
00:57:32.556 --> 00:57:35.462 Yet to keep the the comma there, yeah, remove the question mark
00:57:35.462 --> 00:57:35.826 as well.
00:57:41.106 --> 00:57:46.646 Yeah. OK, save that and then search the searching project. So
00:57:46.646 --> 00:57:48.076 control shift F.
00:57:52.376 --> 00:57:56.261 And search for percent 20 in the current project and see if it's
00:57:56.261 --> 00:57:57.696 happening anywhere else.
00:58:21.226 --> 00:58:21.576 OK.
00:58:23.336 --> 00:58:24.546 So now.
00:58:23.536 --> 00:58:26.425 And then once you, once you've made all those, were there any
00:58:26.425 --> 00:58:28.896 other ones? Sorry, I stepped away for just a second.
00:58:29.946 --> 00:58:30.376 No.
00:58:30.646 --> 00:58:34.521 OK, now you can right click the searching project and just do
00:58:34.521 --> 00:58:36.146 build rather than rebuild.
00:58:35.646 --> 00:58:35.976 OK.
00:58:36.836 --> 00:58:40.256 And the the telltale sign here that you want to look for, go to
00:58:40.256 --> 00:58:41.966 the output tab on Visual Studio.
00:58:43.386 --> 00:58:46.926 Well, you want to look for specifically. OK, that's weird
00:58:46.926 --> 00:58:50.467 that it said it built two things, but it's probably not a
00:58:50.467 --> 00:58:50.956 problem.
00:58:51.716 --> 00:58:52.326 Probably.
00:58:52.646 --> 00:58:55.506 It'll build more than one thing at there's a dependency.
00:58:54.686 --> 00:58:57.977 Yeah, well, typically typically wouldn't. It shouldn't have
00:58:57.977 --> 00:59:01.323 changed anything in that core project since we didn't modify
00:59:01.323 --> 00:59:04.779 any files there. So it should have just said one succeeded and
00:59:04.779 --> 00:59:08.344 then X up to date. So it's weird that it it built, but it should
00:59:08.344 --> 00:59:09.716 be fine. I think it's OK.
00:59:11.536 --> 00:59:14.430 OK, now let's fire up the site. Typically, that's what you want
00:59:14.430 --> 00:59:17.099 to look for if you're doing a light build on like a client
00:59:17.099 --> 00:59:19.858 override or anything else. Do you want it to say 1 succeeded
00:59:19.858 --> 00:59:21.396 and then all the rest up to date?
00:59:22.856 --> 00:59:25.656 But I I think we'll be fine in this case.
00:59:26.496 --> 00:59:28.726 We'll see. If not, I guess.
00:59:30.666 --> 00:59:31.696 Yet another rebuild.
00:59:34.566 --> 00:59:36.436 But let's let's give it a shot.
01:00:43.846 --> 01:00:44.946 Are there other?
01:00:47.676 --> 01:00:49.426 We're gonna test the city.
01:00:50.396 --> 01:00:52.306 Right, so it was.
01:00:51.446 --> 01:00:54.378 We probably, I think there may be some code on the front end
01:00:54.378 --> 01:00:57.359 that's replacing spaces with percent 20s as well. I feel like
01:00:57.359 --> 01:00:59.186 I remember seeing that at some point.
01:01:01.306 --> 01:01:04.270 Let's see. Let's see if we get any better results with this
01:01:04.270 --> 01:01:06.246 one. We may need to reindex to be sure.
01:02:34.146 --> 01:02:37.756 Might want to clear the cache to Redis cache.
01:02:41.486 --> 01:02:43.876 For anything and it works.
01:03:02.356 --> 01:03:02.886 Ohh.
01:03:18.816 --> 01:03:19.536 Yeah, it broke it.
01:03:28.666 --> 01:03:30.956 And automatically capitalizes the 1st letter.
01:03:34.976 --> 01:03:35.766 Apparently.
01:03:38.336 --> 01:03:41.045 But as you type something and then go back to the beginning of
01:03:38.896 --> 01:03:39.446 Ohh.
01:03:41.045 --> 01:03:41.906 the line and delete.
01:03:46.516 --> 01:03:46.896 Yep.
01:03:48.286 --> 01:03:48.826 OK.
01:03:50.176 --> 01:03:50.426 Look.
01:03:57.696 --> 01:03:58.826 We can't test that.
01:03:58.906 --> 01:03:59.156 Good.
01:04:02.426 --> 01:04:03.076 So.
01:04:07.346 --> 01:04:10.254 That's fine because we're too lowering the query on the back
01:04:10.254 --> 01:04:10.636 end too.
01:04:11.306 --> 01:04:14.223 Yeah, I was just gonna see if it was. If it was affecting
01:04:14.223 --> 01:04:14.676 anything.
01:04:18.486 --> 01:04:22.736 Yeah, nothing funny Cert city search. Let's see if it.
01:04:26.386 --> 01:04:28.356 Make sure that break altogether, right?
01:04:38.116 --> 01:04:40.966 Yeah, well, that's not related to the changes we just made.
01:04:41.916 --> 01:04:42.406 No.
01:04:44.156 --> 01:04:44.956 That's sure not.
01:04:48.426 --> 01:04:52.066 Sales Representative tech representative comes up.
01:05:09.676 --> 01:05:13.046 Tell me, am I high or didn't other pop up here?
01:05:16.996 --> 01:05:19.546 I thought it did, but we didn't change anything with that.
01:05:20.246 --> 01:05:20.886 No.
01:05:25.486 --> 01:05:25.946 OK.
01:05:26.746 --> 01:05:31.146 Uh tech representative and we could all sales representatives.
01:05:32.546 --> 01:05:33.686 And a collision tag.
01:05:33.786 --> 01:05:35.836 OK. Real quick before anything else.
01:05:36.576 --> 01:05:37.146 Yeah.
01:05:36.666 --> 01:05:40.220 Look at the response to the most recent query call. Click on that
01:05:40.220 --> 01:05:40.436 one.
01:05:40.446 --> 01:05:40.746 OK.
01:05:42.556 --> 01:05:42.886 OK.
01:05:44.426 --> 01:05:46.913 Yeah, make this a little bit wider so we can see what's going
01:05:46.913 --> 01:05:47.796 on, go to the preview.
01:05:50.036 --> 01:05:50.906 Expand.
01:05:50.986 --> 01:05:52.316 Uh.
01:05:55.636 --> 01:05:56.326 Never mind.
01:06:02.376 --> 01:06:03.156 We're looking for.
01:06:03.976 --> 01:06:07.057 Ohh I was looking for hits metadata scores but it's all
01:06:07.057 --> 01:06:10.523 zero or it's it's an empty array and that's the problem is I'm
01:06:10.523 --> 01:06:13.328 guessing that tech representative probably matches
01:06:13.328 --> 01:06:16.629 better than anything else, but the results aren't sorted at
01:06:16.629 --> 01:06:20.095 all, they're just they're just whatever random order they come
01:06:20.095 --> 01:06:21.086 from the back end.
01:06:22.246 --> 01:06:25.278 Tech representative probably has the highest score and thus
01:06:25.278 --> 01:06:26.996 should be sorted to the top. But.
01:06:28.196 --> 01:06:30.946 It's not sorted by anything I'm guessing.
01:06:34.716 --> 01:06:37.606 It's. I guess it says it's sorted by recent up there.
01:06:40.066 --> 01:06:40.416 Yeah.
01:06:44.916 --> 01:06:47.736 Ohh, sorting was what OK.
01:07:03.706 --> 01:07:06.056 But we still don't get anything hits metadata scores.
01:07:11.656 --> 01:07:15.086 Yeah. Which I guess, I mean, if they're only filtering by newest
01:07:15.086 --> 01:07:18.095 and oldest that match, then that's fine, but we probably
01:07:18.095 --> 01:07:18.676 need to do.
01:07:19.816 --> 01:07:23.060 Were filled. We're we're whatever you select for the job
01:07:23.060 --> 01:07:26.361 title is being passed in the search term term equals tech
01:07:26.361 --> 01:07:28.866 representative in the header or in the URL.
01:07:29.766 --> 01:07:30.186 Yeah.
01:07:31.106 --> 01:07:34.236 That's not the way that we would probably want to do that.
01:07:35.896 --> 01:07:39.633 We should send there should be a job title filter and it should
01:07:39.633 --> 01:07:42.844 be a like a a single thing similar to the city one. It
01:07:42.844 --> 01:07:44.596 would be the exact same thing.
01:07:45.816 --> 01:07:48.966 That way it exactly matches what you pass in.
01:07:50.766 --> 01:07:53.687 And doesn't use like the fuzzy string matching that gives you
01:07:53.687 --> 01:07:55.996 different stuff. That's sort of kind of matches.
01:07:57.186 --> 01:08:00.659 And then we still need to figure out why cities decided to not
01:07:58.176 --> 01:07:58.686 So.
01:08:00.659 --> 01:08:01.376 work anymore.
01:08:03.396 --> 01:08:03.726 Umm.
01:08:04.916 --> 01:08:06.316 Should it be passing the?
01:08:08.606 --> 01:08:09.416 City in the.
01:08:11.126 --> 01:08:11.726 You URL.
01:08:13.456 --> 01:08:16.750 Umm, yes. Any any filters you select over there on the left
01:08:16.750 --> 01:08:18.946 side. Those should be added to the URL.
01:08:20.096 --> 01:08:20.526 And OK.
01:08:20.586 --> 01:08:23.740 So that's a problem with the front end catalog code that
01:08:23.740 --> 01:08:26.895 needs to be fixed, because that's why the catalog filter
01:08:26.895 --> 01:08:29.496 state keeps randomly refreshing or going away.
01:08:30.246 --> 01:08:30.906 Umm.
01:08:32.046 --> 01:08:35.491 It's because the state isn't being preserved correctly, and
01:08:35.491 --> 01:08:38.993 that also means that you can't reliably link other people to
01:08:38.993 --> 01:08:42.439 the site to different pages in the catalog or anything like
01:08:42.439 --> 01:08:42.726 that.
01:08:49.886 --> 01:08:50.416 OK.
01:08:51.766 --> 01:08:52.346 So.
01:08:55.506 --> 01:08:57.596 Can you not click into this job card?
01:08:59.836 --> 01:09:01.426 I guess not.
01:09:09.146 --> 01:09:11.797 I would imagine not. If it's, uh, doesn't look like it has a
01:09:11.797 --> 01:09:12.536 link or anything.
01:09:13.266 --> 01:09:13.916 Umm.
01:09:15.026 --> 01:09:18.866 But I guess what we probably want to do to see why the city
01:09:18.866 --> 01:09:22.963 staff not working is we should probably go ahead and attach and
01:09:22.963 --> 01:09:26.803 throw a break point in that cities filter and see what what
01:09:26.803 --> 01:09:29.556 data we get that actually gets into there.
01:09:30.416 --> 01:09:32.426 So for now, attached to the store front.
01:09:30.616 --> 01:09:30.876 Right.
01:09:33.716 --> 01:09:37.302 We may, we may attach to admin if everything about the actual
01:09:37.302 --> 01:09:38.286 query looks good.
01:09:38.956 --> 01:09:41.666 Umm. Then we'll look at how it indexes.
01:09:42.756 --> 01:09:47.226 And go from there. So we're gonna go into the search module.
01:09:49.266 --> 01:09:51.736 For my dump reader. OK, so I don't want this one.
01:09:52.366 --> 01:09:52.886 Not yet.
01:09:52.936 --> 01:09:54.156 Search, yeah.
01:09:54.266 --> 01:09:57.526 Yeah, F-12 on that cities single query modification.
01:09:59.176 --> 01:10:03.156 OK. And then put a break point, uh, online 42.
01:10:04.726 --> 01:10:08.761 Yeah. OK. So now search for a city and we'll make sure that we
01:10:08.761 --> 01:10:10.106 hit that break point.
01:10:12.306 --> 01:10:12.496 Yep.
01:10:13.026 --> 01:10:16.936 OK, cool. So mouse over form dot city.
01:10:19.716 --> 01:10:20.266 Georgetown.
01:10:20.016 --> 01:10:22.826 OK, that is in fact what you typed in. That's good.
01:10:23.536 --> 01:10:27.713 Trimming too lower. OK in the in the watch list on the bottom
01:10:24.316 --> 01:10:24.666 Yeah.
01:10:27.713 --> 01:10:29.196 left of Visual Studio.
01:10:30.626 --> 01:10:33.976 Type in form dot city dot trim dot to lower.
01:10:36.406 --> 01:10:38.346 Just like we have it on line 47.
01:10:39.566 --> 01:10:43.029 We'll make sure that that doesn't, like, totally mutilate
01:10:43.029 --> 01:10:45.896 that string and make it not make sense anymore.
01:10:46.586 --> 01:10:47.826 Yeah. OK, that looks good.
01:10:49.686 --> 01:10:51.156 So that looks fine.
01:10:52.036 --> 01:10:53.286 And.
01:10:56.996 --> 01:10:59.984 I'm wondering if we need to get rid of that suffix keyword part,
01:10:59.984 --> 01:11:00.766 but I don't know.
01:11:05.446 --> 01:11:06.216 Type in.
01:11:12.466 --> 01:11:17.584 Put a any string in the in the. Actually do form dot city dot
01:11:17.584 --> 01:11:19.566 suffix and then keyword.
01:11:20.256 --> 01:11:21.676 And let's see what that spits out.
01:11:28.256 --> 01:11:30.916 Yeah. And then keyword with the capital K, yeah.
01:11:31.416 --> 01:11:31.776 Ohh.
01:11:39.006 --> 01:11:40.936 Interesting capitalized it.
01:11:49.096 --> 01:11:51.146 Well, this happens in later, right?
01:11:53.146 --> 01:11:55.556 Too low or happens after suffix.
01:11:53.586 --> 01:11:57.330 So what we're doing, so the term the term on the left side is
01:11:57.330 --> 01:12:01.256 contact city dot suffix keyword which is apparently capitalizing
01:12:01.256 --> 01:12:02.766 whatever contact city is.
01:12:03.606 --> 01:12:04.266 And.
01:12:05.066 --> 01:12:09.006 We're trimming into lowering our query form dot city on the right
01:12:09.006 --> 01:12:12.409 side, so that's why they're not matching is because it's
01:12:10.586 --> 01:12:11.176 Yeah.
01:12:12.409 --> 01:12:15.216 recapitalizing with that suffix keyword thing.
01:12:21.686 --> 01:12:23.726 We could have trim dot.
01:12:24.756 --> 01:12:25.646 To lower here.
01:12:26.996 --> 01:12:29.036 Or just remove the suffix.
01:12:31.726 --> 01:12:33.516 Remove hour trip got too low.
01:12:31.896 --> 01:12:36.245 I would, I would think we would just remove the suffix keyword
01:12:36.245 --> 01:12:40.595 part from the search, but let's try that. Let's you know worse
01:12:40.595 --> 01:12:44.738 comes to worse. We can add it back if it doesn't do what we
01:12:44.738 --> 01:12:45.636 expect it to.
01:12:51.146 --> 01:12:52.176 I'm not sure.
01:12:54.436 --> 01:12:56.775 But that would be needed for backspace one more time. We
01:12:56.775 --> 01:12:58.786 don't need the exclamation point, I don't think.
01:13:00.216 --> 01:13:04.186 OK. And then kill the app pools and then just a build on this uh
01:13:04.186 --> 01:13:05.286 searching project?
01:13:16.796 --> 01:13:17.946 Better plug up here.
01:13:20.716 --> 01:13:23.664 I don't know what the heat on in this House is, but I have for
01:13:23.664 --> 01:13:24.226 reasons I'm.
01:13:25.616 --> 01:13:28.846 I feel that perpetual coldness.
01:13:26.356 --> 01:13:26.606 Alright.
01:13:30.766 --> 01:13:35.228 It's it was 70 was like 77 in my in my room in here earlier this
01:13:30.876 --> 01:13:31.416 Yeah.
01:13:35.228 --> 01:13:36.876 morning and I was still.
01:13:38.406 --> 01:13:42.076 Huddled in a ball, feeling feeling mighty cold.
01:13:40.876 --> 01:13:41.486 Feels.
01:13:43.226 --> 01:13:45.896 He's like it's about 67 years.
01:13:46.116 --> 01:13:50.143 Yeah. Also, whenever this spins up, let's clear the Redis cache
01:13:50.143 --> 01:13:50.836 just to be.
01:13:51.476 --> 01:13:51.896 OK.
01:13:51.996 --> 01:13:53.636 Be sure that we're getting fresh results.
01:13:54.416 --> 01:13:56.156 Wait until it spins up or do it now.
01:13:56.796 --> 01:13:57.546 I just wait.
01:13:58.466 --> 01:13:58.746 OK.
01:13:59.016 --> 01:14:01.957 Just in case it fires off the request while you're in there
01:14:01.957 --> 01:14:02.546 clearing it.
01:14:03.416 --> 01:14:07.303 Or wait until the page fully loads and knowing that this will
01:14:07.303 --> 01:14:11.002 probably be stale results. OK now go in and then clear the
01:14:11.002 --> 01:14:12.006 Redis cache and.
01:14:28.336 --> 01:14:29.606 Why didn't that clear the filter?
01:14:30.896 --> 01:14:31.776 Because it's in the header.
01:14:32.676 --> 01:14:35.830 That's in your URL. That's not part of the Redis cache
01:14:34.776 --> 01:14:36.516 Yeah, yeah.
01:14:35.830 --> 01:14:36.346 anything.
01:14:37.886 --> 01:14:40.686 Yeah, that makes sense. OK.
01:14:39.996 --> 01:14:41.396 Which is how it's supposed to be.
01:14:41.986 --> 01:14:42.386 Right.
01:14:46.826 --> 01:14:47.316 Austin.
01:14:48.476 --> 01:14:51.189 Three of them with us. And what about the the dairy in one was
01:14:49.016 --> 01:14:50.126 We get asked.
01:14:51.189 --> 01:14:53.902 the one we were only seeing 21 result when it should have been
01:14:53.902 --> 01:14:55.496 two. So let's see if that works now.
01:14:58.036 --> 01:14:58.766 One result?
01:14:59.386 --> 01:14:59.776 Huh.
01:15:00.756 --> 01:15:02.226 I wonder what it is about me.
01:15:04.316 --> 01:15:05.536 So we have.
01:15:07.196 --> 01:15:07.996 Darien.
01:15:08.966 --> 01:15:09.726 And then.
01:15:15.446 --> 01:15:17.726 I guess it's on another page now. Why can't I not?
01:15:21.136 --> 01:15:24.337 That pagination looks wrong too, cause you definitely scroll
01:15:22.566 --> 01:15:23.036 Ohh.
01:15:24.337 --> 01:15:27.696 through more than eight things, I think unless the lag was just
01:15:27.696 --> 01:15:29.796 making it look like it was more than I.
01:15:36.306 --> 01:15:38.806 So this should be every job that I have.
01:15:39.706 --> 01:15:41.486 Austin Austin, there's Darian.
01:15:44.146 --> 01:15:48.599 Georgetown, Houston, Hollywood. Where's the dairy equine? There?
01:15:48.599 --> 01:15:50.106 There were definitely.
01:15:48.726 --> 01:15:50.276 There were definitely too earlier.
01:15:51.436 --> 01:15:51.876 Huh.
01:15:55.096 --> 01:15:58.184 Let's look and see. This should be there's no filters applied.
01:15:58.184 --> 01:16:00.146 This should be every single job, right?
01:16:01.126 --> 01:16:01.656 So.
01:16:01.536 --> 01:16:05.337 Every job that got correctly indexed, maybe it didn't index
01:16:05.337 --> 01:16:09.139 correctly. Wanna let's do a check real fast in the database
01:16:09.139 --> 01:16:09.646 and see.
01:16:10.656 --> 01:16:11.326 Umm.
01:16:13.286 --> 01:16:15.616 Well, all we have in there for jobs.
01:16:13.946 --> 01:16:14.286 I have.
01:16:17.156 --> 01:16:18.176 All these are jobs.
01:16:18.696 --> 01:16:22.466 Ohh, that's a lot more than I was expecting. OK.
01:16:23.906 --> 01:16:27.230 So then we need to figure out why most of them aren't showing
01:16:27.230 --> 01:16:28.196 up in the catalog.
01:16:28.886 --> 01:16:33.140 Something is skipping them in the in the indexer or something
01:16:33.140 --> 01:16:34.376 about the queries.
01:16:35.686 --> 01:16:36.766 Not functional.
01:16:41.056 --> 01:16:43.246 Could also just be that the pagination is broken.
01:16:45.406 --> 01:16:45.736 Yeah.
01:16:45.636 --> 01:16:49.840 Let's go back to the the site real fast and let's check the
01:16:49.840 --> 01:16:54.185 actual response on that call to query the most recent call to
01:16:54.185 --> 01:16:55.026 query, yeah.
01:16:57.116 --> 01:16:58.746 The other preview tab is easier, yeah.
01:17:02.576 --> 01:17:06.823 Total pages one total count 8 OK. So unless there's something
01:17:06.823 --> 01:17:11.276 going on in the back end that's mangling that response before it
01:17:11.276 --> 01:17:14.976 gets sent out, then it really did only find 8 things.
01:17:16.076 --> 01:17:17.136 Expand form.
01:17:21.396 --> 01:17:24.812 Yeah, we're not sending any filters. We're not. We're even
01:17:24.812 --> 01:17:28.054 asking for 9 things. So it didn't even find a full page
01:17:28.054 --> 01:17:31.296 worth of responses. So that means that there's probably
01:17:31.296 --> 01:17:34.943 something that's filtering out those responses in the indexer.
01:17:34.943 --> 01:17:37.086 So let's go look at the dump reader.
01:17:44.986 --> 01:17:46.716 OK, so uh wait, scroll back down.
01:17:49.406 --> 01:17:51.506 So yeah, starting here is where we want to be.
01:17:53.266 --> 01:17:57.004 So this is checking that the yeah their status key has to be
01:17:53.306 --> 01:17:54.706 So approved.
01:17:57.004 --> 01:18:00.682 approved. So figure out which one of those it's supposed to
01:18:00.682 --> 01:18:00.866 be.
01:18:02.656 --> 01:18:04.266 So it would be.
01:18:03.856 --> 01:18:08.173 This is going to be all these status ID column ohly whichever
01:18:07.716 --> 01:18:09.746 Yeah. So it's ones.
01:18:08.173 --> 01:18:09.566 ones are showing up.
01:18:10.816 --> 01:18:11.746 Ones are approved.
01:18:11.086 --> 01:18:15.824 Well, no. Well, no. I was gonna say there's multiple of there's
01:18:13.006 --> 01:18:15.356 No, no, couldn't be. Yeah, you're right.
01:18:15.824 --> 01:18:19.896 not. Well, maybe it's Two's that, or there's only two.
01:18:19.226 --> 01:18:22.750 Yeah, you can just do do a quick Umm select star from. Yeah,
01:18:20.886 --> 01:18:21.456 I know.
01:18:22.750 --> 01:18:24.426 jobs, dot job status and see.
01:18:38.846 --> 01:18:40.686 Wait, there is no job status.
01:18:39.056 --> 01:18:40.266 And then you can F.
01:18:42.046 --> 01:18:45.616 I totally right. Yeah. It's probably job opening status.
01:18:49.646 --> 01:18:51.406 Yeah, job openings status, yeah.
01:18:49.926 --> 01:18:50.696 There it is, yeah.
01:18:53.836 --> 01:18:54.386 OK.
01:18:59.946 --> 01:19:04.788 Approved was the one looking for. Was one. OK, cool. Alright
01:19:00.506 --> 01:19:01.716 We need one.
01:19:03.166 --> 01:19:03.606 1.
01:19:04.788 --> 01:19:05.026 so.
01:19:06.666 --> 01:19:09.449 Let's start building a building. A query here that will return to
01:19:09.449 --> 01:19:11.853 us everything. The indexer should get. So backspace what
01:19:11.853 --> 01:19:12.866 you've just highlighted.
01:19:13.766 --> 01:19:17.756 And do a select star from jobs dot job opening.
01:19:21.756 --> 01:19:24.957 And then the next line down, we're going to add a where
01:19:24.957 --> 01:19:25.986 active equals one.
01:19:27.696 --> 01:19:31.906 So we already saw that it has a filter by active next line down.
01:19:32.016 --> 01:19:32.306 Ohh.
01:19:32.746 --> 01:19:33.836 Uh. Yeah. And.
01:19:34.746 --> 01:19:36.736 Status ID equals one.
01:19:40.046 --> 01:19:42.197 OK. And then let's go back to the code and see what else it's
01:19:42.197 --> 01:19:42.406 doing.
01:19:48.026 --> 01:19:49.876 OK, it also has.
01:19:49.076 --> 01:19:50.586 Order by ID.
01:19:50.626 --> 01:19:54.122 It also has a filter by type keys, but that may not be set on
01:19:54.122 --> 01:19:57.676 anything, so let's click on that key list and then F-12 to see
01:19:57.676 --> 01:19:59.086 where that's being built.
01:20:03.486 --> 01:20:03.736 Here.
01:20:04.076 --> 01:20:07.901 And then it loads those keys from search job opening index,
01:20:07.901 --> 01:20:10.196 filter by type keys. So on line 25.
01:20:13.266 --> 01:20:16.773 Yeah, click on that F-12, make sure that it doesn't have a
01:20:16.773 --> 01:20:17.606 default value.
01:20:18.646 --> 01:20:21.142 Yeah, OK. It's null alright. That should be fine. Then I
01:20:21.142 --> 01:20:23.813 doubt you have that in your app settings. We could check for
01:20:23.813 --> 01:20:26.266 sanity if we want to, but I think that's probably fine.
01:20:27.196 --> 01:20:29.966 If I copied the app settings straight from QA.
01:20:29.586 --> 01:20:32.987 OK, let's check client and environment. Those would be the
01:20:32.987 --> 01:20:35.466 ones that might have that, but I doubt it.
01:20:35.726 --> 01:20:37.016 And what was the?
01:20:38.816 --> 01:20:43.686 Go back to that config and see what that was called is.
01:20:45.256 --> 01:20:45.666 Here.
01:20:46.946 --> 01:20:48.336 Right. No, that's not it.
01:20:48.776 --> 01:20:49.196 No.
01:20:50.006 --> 01:20:52.176 Yeah, yeah.
01:20:52.876 --> 01:20:55.136 Just go back to dump reader and have 12 back into it.
01:20:53.246 --> 01:20:53.936 I guess it.
01:20:54.896 --> 01:20:55.456 Yeah.
01:20:56.676 --> 01:20:58.886 It was one of the like, temporary open files.
01:20:59.896 --> 01:21:00.276 Yeah.
01:21:05.956 --> 01:21:06.896 I guess I didn't open.
01:21:08.586 --> 01:21:08.926 Yeah.
01:21:11.026 --> 01:21:14.139 OK, that's not in there. And then check, uh, environment just
01:21:14.139 --> 01:21:17.152 for sanity. That's definitely not in there. OK, cool. So we
01:21:16.266 --> 01:21:16.966 It's not here.
01:21:17.152 --> 01:21:20.316 don't have to worry about that. That's not getting in the way.
01:21:18.036 --> 01:21:18.476 Yeah.
01:21:21.096 --> 01:21:24.386 Umm alright, so back to the code.
01:21:26.016 --> 01:21:29.346 Umm, that's all the Yep dump reader.
01:21:27.626 --> 01:21:28.266 Dump reader.
01:21:30.516 --> 01:21:33.809 That's all the initial filters that it's applying. Let's scroll
01:21:33.809 --> 01:21:36.897 past all of this and see what other stuff it's doing inside
01:21:36.897 --> 01:21:39.316 the method. The very first thing is it checks.
01:21:40.246 --> 01:21:43.936 If the versions title is not a valid key, which basically just
01:21:43.936 --> 01:21:47.276 means if it's an empty string or null, then it skips it.
01:21:49.376 --> 01:21:53.466 So let's go back into the SQL query input and title.
01:21:58.266 --> 01:21:59.026 Uh.
01:22:00.276 --> 01:22:01.726 Not equal to null.
01:22:01.596 --> 01:22:02.416 Equal.
01:22:02.586 --> 01:22:06.241 And you just do not like the. Yeah, exclamation point equal
01:22:03.946 --> 01:22:04.236 No.
01:22:06.241 --> 01:22:06.546 null.
01:22:09.516 --> 01:22:10.026 They think.
01:22:10.276 --> 01:22:11.696 Or empty string.
01:22:12.676 --> 01:22:16.644 I don't know how to do that. One is title not a a field on this
01:22:16.644 --> 01:22:17.016 table.
01:22:20.006 --> 01:22:20.856 Yeah, it is right here.
01:22:20.056 --> 01:22:23.942 Maybe it's maybe it's job title. Ohly totally. OK. Why is it
01:22:23.942 --> 01:22:25.026 complaining then?
01:22:26.806 --> 01:22:29.016 Because that syntax is wrong probably.
01:22:29.346 --> 01:22:31.376 Yeah, probably. I'm not very good at sequel.
01:22:30.026 --> 01:22:30.236 The.
01:22:31.486 --> 01:22:34.476 And title is not null.
01:22:36.196 --> 01:22:36.816 That works.
01:22:37.546 --> 01:22:39.016 Cool. OK, I.
01:22:38.166 --> 01:22:39.176 And.
01:22:39.966 --> 01:22:40.986 Title is.
01:22:42.766 --> 01:22:45.846 Thought he could. No, I was gonna say.
01:22:46.876 --> 01:22:49.646 It's not equal to.
01:22:51.086 --> 01:22:53.266 A single tick for strings and SQL.
01:22:51.366 --> 01:22:51.876 That work.
01:22:56.576 --> 01:22:59.659 Sure, let's give that a shot. So highlight that whole query and
01:22:59.659 --> 01:23:01.056 let's see what we get for it.
01:23:02.376 --> 01:23:04.981 This should give us back everything. OK, so there's a
01:23:04.981 --> 01:23:07.056 number of them that it should be indexing.
01:23:07.886 --> 01:23:09.956 But it's not. We're only getting.
01:23:09.316 --> 01:23:10.286 When he's three of them.
01:23:10.726 --> 01:23:13.779 Eight of them back. All right. So let's go back in the code and
01:23:13.779 --> 01:23:16.354 see if there's any other conditions or like potential
01:23:16.354 --> 01:23:18.406 early early outs or skips that it's doing.
01:23:19.246 --> 01:23:22.561 So let's Scroll down and look for any use of continue in this
01:23:22.561 --> 01:23:23.256 in this loop.
01:23:26.946 --> 01:23:27.716 Gift culture.
01:23:37.806 --> 01:23:38.216 No.
01:23:39.876 --> 01:23:44.096 Just index is everything and moves on with its life doesn't.
01:23:46.046 --> 01:23:49.436 Doesn't have any other possible conditions, so it's.
01:24:03.546 --> 01:24:04.026 Umm.
01:24:05.546 --> 01:24:07.976 OK, let's check.
01:24:09.346 --> 01:24:13.569 The service for the job opening search. So if we go back into
01:24:13.569 --> 01:24:15.136 the searching provider.
01:24:16.856 --> 01:24:17.586 Uh.
01:24:19.496 --> 01:24:25.787 Elastic Serge jobs. There should be a uh, sorry, yeah. Service
01:24:25.787 --> 01:24:26.986 right there.
01:24:28.286 --> 01:24:30.806 OK, let's go look at how it actually calls this, because I'm
01:24:30.806 --> 01:24:33.286 wondering now if it's like modifying the form or something.
01:24:33.986 --> 01:24:37.389 Either when it gets returned or before it, it actually runs the
01:24:37.389 --> 01:24:40.208 search. If it's like doing something in there that's
01:24:40.208 --> 01:24:40.846 altering it.
01:24:41.986 --> 01:24:44.166 Because we've confirmed that your database has.
01:24:45.296 --> 01:24:48.403 More than eight things that it should be indexing based on all
01:24:48.403 --> 01:24:50.376 the filtering that we're applying here.
01:24:54.356 --> 01:24:55.756 And I'm not entirely sure.
01:24:54.816 --> 01:24:55.936 It is calling.
01:24:57.806 --> 01:25:00.146 Where is it? Where was it making that call to?
01:24:58.946 --> 01:25:01.731 So we'll go back in that this the searching service that we
01:25:01.731 --> 01:25:04.656 were looking at, it's gonna be down toward the bottom of this.
01:25:07.246 --> 01:25:07.566 OK.
01:25:09.216 --> 01:25:12.239 So that's the index. We don't care as much about that. We
01:25:12.239 --> 01:25:13.856 wanna mostly look at the query.
01:25:15.256 --> 01:25:18.666 Keep scrolling, that one's suggest should be the next one.
01:25:19.386 --> 01:25:23.241 Yeah. OK, search. OK. So creates pricing factory context. That's
01:25:23.241 --> 01:25:26.682 all fine. I'm actually pretty sure we don't need that for
01:25:26.682 --> 01:25:28.936 this, but that doesn't really matter.
01:25:30.536 --> 01:25:34.366 Original query equals request dot query, original city equals
01:25:34.366 --> 01:25:35.416 request dot city.
01:25:36.556 --> 01:25:37.596 If the.
01:25:38.486 --> 01:25:42.346 Now it replaces spaces in the original query with string dot
01:25:42.346 --> 01:25:42.726 empty.
01:25:44.476 --> 01:25:47.046 It appends all of them together, all the words together.
01:25:48.796 --> 01:25:49.396 Yeah.
01:25:50.196 --> 01:25:51.136 Let's get rid of that.
01:25:54.616 --> 01:25:56.026 So just this whole after.
01:25:56.466 --> 01:25:59.722 Yeah, I don't think it's. I don't think that it should be
01:25:59.722 --> 01:26:02.136 altering the query that the user sends in.
01:26:03.116 --> 01:26:03.646 Umm.
01:26:05.466 --> 01:26:09.064 Let me make sure that it's not doing that. Like maybe that was
01:26:09.064 --> 01:26:12.262 copied in from the from like the product search code or
01:26:12.262 --> 01:26:15.746 something, but I don't think so. I'm pretty sure that we we.
01:26:17.256 --> 01:26:19.839 We don't alter the what the what the person's trying to search
01:26:19.839 --> 01:26:21.726 for because that would throw the results off.
01:26:25.556 --> 01:26:28.678 Yeah, that's not in there. So let's, yeah, let's let's keep
01:26:28.678 --> 01:26:32.060 that going for now. What is the original city used for? Click on
01:26:32.060 --> 01:26:34.506 that and see maybe it's not used for anything.
01:26:35.806 --> 01:26:38.445 Scroll around and it's got something highlighted a little
01:26:38.445 --> 01:26:40.766 bit lower. Click on it again and then Scroll down.
01:26:42.146 --> 01:26:45.768 You can see on the right side on your scroll bar it gives it a
01:26:43.906 --> 01:26:45.496 Ohh yeah, I see it. Yeah.
01:26:45.768 --> 01:26:46.976 little white outline.
01:26:48.236 --> 01:26:48.716 Yeah.
01:26:49.736 --> 01:26:50.186 OK.
01:26:51.456 --> 01:26:52.306 So.
01:27:00.116 --> 01:27:03.196 Original City gets requests city and then.
01:27:03.366 --> 01:27:06.514 And then sets it back on the view models form, which we don't
01:27:03.906 --> 01:27:04.526 Here.
01:27:06.514 --> 01:27:09.611 need to do both of those two can be can be removed. The view
01:27:09.611 --> 01:27:11.846 model, form query and view model form city.
01:27:12.796 --> 01:27:16.289 Yeah, we can keep the roles. Anyone again, that one doesn't
01:27:16.289 --> 01:27:17.396 really matter, but.
01:27:18.986 --> 01:27:19.486 OK.
01:27:20.676 --> 01:27:22.166 And then get rid of these two.
01:27:22.976 --> 01:27:23.936 Yeah.
01:27:25.206 --> 01:27:26.306 We don't need those, right?
01:27:27.346 --> 01:27:28.156 Wrecked.
01:27:31.146 --> 01:27:32.186 I guess I should have.
01:27:32.916 --> 01:27:34.116 Comment that out.
01:27:34.156 --> 01:27:35.166 Yeah, it's fine.
01:27:36.446 --> 01:27:36.886 OK.
01:27:37.806 --> 01:27:41.606 Get history is there for us to pull it from if we need it, but.
01:27:42.256 --> 01:27:42.606 You should.
01:27:43.616 --> 01:27:47.226 Uh, so now build searching. Wait.
01:27:43.666 --> 01:27:45.076 I suspect we won't.
01:27:47.676 --> 01:27:49.786 App pools. Yep, good catch.
01:27:50.956 --> 01:27:51.646 Umm.
01:27:52.746 --> 01:27:56.862 No, I would say this still doesn't really give us any
01:27:56.862 --> 01:28:01.436 indication of why the why we weren't seeing enough results.
01:28:02.396 --> 01:28:03.486 So.
01:28:04.106 --> 01:28:04.856 Umm.
01:28:09.306 --> 01:28:14.786 Go back into the search module for uh jobs. Scroll down more.
01:28:17.046 --> 01:28:17.756 Let's see it.
01:28:18.466 --> 01:28:21.834 Search view model additional assignments for cities. Click on
01:28:21.834 --> 01:28:22.866 that and then F-12.
01:28:26.166 --> 01:28:28.516 OK, in that returns all of the cities that are.
01:28:31.046 --> 01:28:34.456 And the result said OK, that's fine, alright.
01:28:34.536 --> 01:28:37.286 Umm yeah, you already do the build.
01:28:38.166 --> 01:28:38.326 No.
01:28:38.806 --> 01:28:39.996 OK, go ahead and build that.
01:28:45.276 --> 01:28:45.776 Thank you.
01:28:46.536 --> 01:28:47.586 Love you. Love you too.
01:28:53.556 --> 01:28:57.138 By the way, for anybody that that needs to drop the R after
01:28:55.026 --> 01:28:55.706 Yeah.
01:28:57.138 --> 01:29:00.780 4:00 o'clock. So feel free if anybody needs to needs to head
01:29:00.780 --> 01:29:03.586 out, no pressure and have a fantastic weekend.
01:29:06.626 --> 01:29:09.136 Actually, I'm gonna pressure you guys. Y'all gonna stay.
01:29:12.866 --> 01:29:14.786 I hope you have a fantastic weekend too.
01:29:16.096 --> 01:29:20.556 Yeah, there he is, man. Mr Silent there today.
01:29:22.486 --> 01:29:23.496 Intuitively.
01:29:24.836 --> 01:29:28.020 That's that's out of character. Do you wanna do you wanna take
01:29:27.086 --> 01:29:28.066 It is, yeah.
01:29:27.216 --> 01:29:28.036 Yeah, we had.
01:29:28.020 --> 01:29:30.396 the floor for 20 minutes? I've I've, you know.
01:29:29.466 --> 01:29:34.163 Yeah, I know. Yeah, we had baby pictures. So I was in the car
01:29:34.163 --> 01:29:35.906 for a good chunk. Yeah.
01:29:34.166 --> 01:29:34.926 Ah, OK.
01:29:35.116 --> 01:29:35.436 Umm.
01:29:37.786 --> 01:29:40.676 Gotcha. Yeah. Try to steal the spotlight. Did you?
01:29:42.816 --> 01:29:44.526 Uh, yes, always.
01:29:48.736 --> 01:29:52.487 All right. Rebuilds. Done. OK, let's fire it up and see. See
01:29:52.487 --> 01:29:54.886 what our results are looking like now.
01:29:53.606 --> 01:29:54.146 Cleared.
01:30:36.166 --> 01:30:37.276 So now.
01:30:40.786 --> 01:30:41.746 We still got 8.
01:30:44.336 --> 01:30:47.266 Uh, OK. Let's try. Uh, let's try a fresh index one more time.
01:30:48.806 --> 01:30:49.036 OK.
01:31:02.356 --> 01:31:05.740 And if we still only see eight after this, I would be, I would
01:31:05.740 --> 01:31:08.426 say, probably the best thing to do at that point.
01:31:09.466 --> 01:31:11.996 James is the elastic search wizard.
01:31:13.686 --> 01:31:17.291 So we may need to get his get his help with this he is better
01:31:17.291 --> 01:31:20.780 at using Kibana than me so he'll be able to show you how to
01:31:20.780 --> 01:31:24.211 actually look at what gets indexed into Kibana. I've never
01:31:24.211 --> 01:31:27.933 been able to get it to work and I'm sure there's just something
01:31:27.933 --> 01:31:29.096 I'm doing wrong but.
01:31:29.816 --> 01:31:31.146 Umm we can.
01:31:30.476 --> 01:31:35.186 Look, all these statuses say pending here, right?
01:31:37.996 --> 01:31:38.936 Well, I guess.
01:31:38.386 --> 01:31:42.874 Sanity check. Can you look at your connection string for your
01:31:42.874 --> 01:31:43.526 for your.
01:31:45.606 --> 01:31:48.988 Local and make sure that it's pointing to the database. We
01:31:45.886 --> 01:31:47.546 Yeah, yeah, yeah.
01:31:48.988 --> 01:31:49.676 think it is.
01:31:50.486 --> 01:31:53.756 Geez, gosh, that's gonna be something it's not.
01:31:55.206 --> 01:31:55.636 Other one.
01:31:55.466 --> 01:31:55.956 Yeah.
01:31:56.816 --> 01:31:59.626 Ohh yeah, the connection strings dot config.
01:31:58.986 --> 01:32:00.256 Yeah, dot config, yeah.
01:32:01.076 --> 01:32:01.616 Yeah.
01:32:03.606 --> 01:32:04.016 Yeah.
01:32:04.826 --> 01:32:07.380 OK. Yeah, it's point your local. Alright, good. Just just to
01:32:07.380 --> 01:32:09.892 Sandy check cause I've I've definitely done that before and
01:32:09.892 --> 01:32:12.404 I'm like, I definitely just checked this and it's right and
01:32:12.404 --> 01:32:14.456 realizing 20 minutes later that is on the wrong.
01:32:12.676 --> 01:32:17.028 Well, I had to migrate QA like yeah, I had to migrate QA like a
01:32:17.028 --> 01:32:21.176 week ago or something and I was like man, it might be on TV,
01:32:17.936 --> 01:32:18.936 Yeah, OK. Yeah.
01:32:21.176 --> 01:32:21.516 yeah.
01:32:21.566 --> 01:32:21.976 Hmm.
01:32:22.576 --> 01:32:23.556 So yeah.
01:32:24.406 --> 01:32:25.316 OK, that's good.
01:32:24.806 --> 01:32:25.406 Uh.
01:32:26.636 --> 01:32:27.186 Yes.
01:32:27.306 --> 01:32:30.993 OK, let's go back into the admin real quick and see if you can
01:32:28.286 --> 01:32:28.686 Uh.
01:32:30.993 --> 01:32:33.686 filter in the admin by status and if you can.
01:32:34.396 --> 01:32:36.486 Choose the approved one and see how many show up.
01:32:38.476 --> 01:32:38.866 6.
01:32:38.936 --> 01:32:41.116 15 of 73.
01:32:38.946 --> 01:32:41.991 OK, I'm guessing that status saying pending in the in the
01:32:41.886 --> 01:32:42.336 Away.
01:32:41.991 --> 01:32:44.616 thing over there. Oh, it didn't. It didn't do it.
01:32:45.936 --> 01:32:46.976 OK. And then click filter.
01:32:48.026 --> 01:32:48.866 Yeah, there we go.
01:32:48.396 --> 01:32:50.126 OK, there we go. Yeah, never mind. OK.
01:32:50.726 --> 01:32:51.776 23 items.
01:32:53.216 --> 01:32:56.776 23 items in total. OK. And how many did you get? Yeah, OK,
01:32:53.986 --> 01:32:54.226 What?
01:32:55.056 --> 01:32:57.696 Yeah, that's the same as the database query.
01:32:56.776 --> 01:33:00.096 alright, cool. Yeah. What? I was gonna check, alright.
01:32:58.456 --> 01:32:59.136 23.
01:33:01.196 --> 01:33:04.441 Well, alright, let's set that index. Then again, and let's
01:33:04.441 --> 01:33:05.706 let's see where we get.
01:33:08.316 --> 01:33:11.827 So if I trust that there's also a scheduled task, the index of
01:33:11.827 --> 01:33:12.106 jobs.
01:33:24.726 --> 01:33:27.616 8 and ohh well, I guess I need to clear the cache.
01:33:26.126 --> 01:33:27.686 Uh, clear the Redis, yeah.
01:33:45.686 --> 01:33:52.229 Swear it looks like more than 812345678. I guess it is a.
01:33:52.229 --> 01:33:55.276 Let's just look here at QA.
01:33:55.926 --> 01:33:59.253 Yeah, maybe this is just, I don't know, this is very
01:33:59.253 --> 01:33:59.756 strange.
01:34:00.976 --> 01:34:03.688 Those kind of shift and are you are you looking at the status
01:34:03.688 --> 01:34:06.269 because that definitely would affect it or did you already
01:34:05.766 --> 01:34:06.096 Yeah.
01:34:06.269 --> 01:34:06.926 eliminate that?
01:34:07.456 --> 01:34:08.296 Yeah, but yeah.
01:34:08.026 --> 01:34:08.586 Yeah.
01:34:09.806 --> 01:34:12.560 We ran through all the filters, the index supplies and created a
01:34:10.026 --> 01:34:10.566 Yeah.
01:34:12.560 --> 01:34:15.144 SQL query that does the same thing and we can see that there
01:34:15.144 --> 01:34:17.136 are 23 records that should be getting indexed.
01:34:17.856 --> 01:34:18.316 Umm.
01:34:19.056 --> 01:34:22.101 And what about the elastic instance? Where is that pointed
01:34:22.101 --> 01:34:22.256 at?
01:34:23.376 --> 01:34:24.826 That is also a good question.
01:34:26.066 --> 01:34:27.546 Umm, so less.
01:34:26.266 --> 01:34:27.686 Check your app settings real quick.
01:34:29.006 --> 01:34:31.429 Let's make sure that you're like your local self instance is
01:34:29.086 --> 01:34:29.456 OK.
01:34:31.429 --> 01:34:33.296 pointed at your local elastic search instance.
01:34:34.056 --> 01:34:34.666 Umm.
01:34:37.106 --> 01:34:40.115 The only way that that might Ohly actually that's a good that
01:34:37.476 --> 01:34:38.296 So.
01:34:40.115 --> 01:34:42.446 might not be the case. Open up uh, environment.
01:34:45.936 --> 01:34:49.496 Umm, OK, it's not in here. Go to the client one.
01:34:51.006 --> 01:34:53.326 And then control F4.
01:34:53.406 --> 01:34:53.776 Here.
01:34:54.316 --> 01:34:58.303 I'm just searching. Yeah, just ordered searching. Should find
01:34:55.736 --> 01:34:56.986 So asked OK.
01:34:58.303 --> 01:34:58.496 it.
01:34:59.966 --> 01:35:01.676 OK, step through here and.
01:35:04.036 --> 01:35:06.997 OK, that's the whole. OK, then, as long as there's no settings
01:35:04.306 --> 01:35:04.766 That's it.
01:35:06.997 --> 01:35:09.912 applied, it should be pointing at your local as you mentioned
01:35:09.912 --> 01:35:12.733 that you copied the settings from QA earlier. So that was I
01:35:12.733 --> 01:35:15.412 should have thought to check that sooner that maybe we'd
01:35:12.736 --> 01:35:13.196 Yeah.
01:35:15.412 --> 01:35:17.246 accidentally put it in the wrong spot.
01:35:18.306 --> 01:35:18.816 But.
01:35:19.576 --> 01:35:20.286 We did not.
01:35:25.406 --> 01:35:25.966 Uh.
01:35:31.766 --> 01:35:32.896 See are you got anymore?
01:35:34.936 --> 01:35:37.176 Call outs because that was when we didn't think of for sure.
01:35:39.176 --> 01:35:41.782 Just normally at that point I would and you guys may have
01:35:41.782 --> 01:35:44.567 already done this, but I would actually look at Elasticsearch
01:35:44.567 --> 01:35:45.736 and see what it has in it.
01:35:46.576 --> 01:35:48.546 Have you done that with Cabana and all that?
01:35:49.826 --> 01:35:52.526 I got cabana loaded up here. I don't really know how to use it.
01:35:53.286 --> 01:35:56.457 Oh, OK yeah, we can do that. If you're still good on time, let's
01:35:56.457 --> 01:35:56.896 shred it.
01:35:57.636 --> 01:35:58.206 Yep.
01:35:57.896 --> 01:35:59.996 I'm. I'm great. I'm golden. Yeah.
01:36:00.146 --> 01:36:03.360 Yep, I'm good. At least for at least for the next 45 minutes.
01:36:00.256 --> 01:36:00.736 OK.
01:36:03.360 --> 01:36:03.516 So.
01:36:05.446 --> 01:36:06.946 Let's see. So then the only other.
01:36:06.196 --> 01:36:09.062 You might hear explicit is in the background. I'll try to
01:36:09.062 --> 01:36:12.126 mute, but I'm on with the sales team in there. They're pretty
01:36:12.126 --> 01:36:12.966 rowdy. I love it.
01:36:12.346 --> 01:36:13.106 Ohh OK.
01:36:15.586 --> 01:36:17.756 You got this sirlion. Go for it so.
01:36:17.036 --> 01:36:19.456 Yep, Yep, I will. I will do my best.
01:36:20.556 --> 01:36:21.486 Alright so.
01:36:22.296 --> 01:36:24.206 I think that's.
01:36:26.386 --> 01:36:29.686 I'm trying to remember there's a way that you can.
01:36:31.186 --> 01:36:31.916 Umm.
01:36:35.246 --> 01:36:38.329 In that console down there you can you put the the index name
01:36:38.329 --> 01:36:38.876 that we're.
01:36:40.406 --> 01:36:43.246 You can get a list of the, yeah.
01:36:40.446 --> 01:36:42.166 That we are creating in Seth.
01:36:44.176 --> 01:36:46.806 And everyone, I'll see if I can find a nuclino and post it fast.
01:36:48.166 --> 01:36:54.161 OK, the index name is job search in job something index search,
01:36:54.161 --> 01:36:59.126 something like that. Is this what we're looking for?
01:36:55.916 --> 01:36:56.366 Umm.
01:36:57.686 --> 01:37:01.174 That should be in the environment file. Yeah, grab
01:37:01.174 --> 01:37:01.516 that.
01:37:02.716 --> 01:37:05.919 And then go back into the thing and just paste that after the
01:37:05.919 --> 01:37:06.126 git.
01:37:10.546 --> 01:37:11.376 Right here.
01:37:12.366 --> 01:37:13.626 Remove under score search.
01:37:14.976 --> 01:37:15.276 OK.
01:37:15.396 --> 01:37:17.376 And then CR also just sent. Uh.
01:37:18.846 --> 01:37:22.790 A couple of links for some useful stuff as well as the
01:37:22.790 --> 01:37:23.866 nuclino itself.
01:37:25.016 --> 01:37:26.486 Which is good.
01:37:27.986 --> 01:37:28.666 It's the.
01:37:29.196 --> 01:37:30.266 Mascoutin Mandarin.
01:37:29.396 --> 01:37:33.746 Cabana stuff is cabana stuff tends to be a little bit.
01:37:34.776 --> 01:37:36.126 Confusing sometimes.
01:37:36.726 --> 01:37:39.036 Gonna hear it, OK.
01:37:42.816 --> 01:37:44.166 Yeah, this is the setup.
01:37:47.796 --> 01:37:48.436 OK.
01:37:51.886 --> 01:37:53.186 And in the.
01:37:54.366 --> 01:37:55.056 Here.
01:37:56.356 --> 01:37:59.626 So we just wanted query match all right like.
01:37:58.486 --> 01:38:01.466 This uh, just click the play button and see what we get.
01:38:03.866 --> 01:38:05.156 See this is.
01:38:04.036 --> 01:38:04.336 OK.
01:38:06.426 --> 01:38:08.616 I think it's gotta be the other one.
01:38:07.546 --> 01:38:08.196 I.
01:38:10.856 --> 01:38:11.606 The.
01:38:12.426 --> 01:38:13.676 Like, it's gotta be this one.
01:38:16.756 --> 01:38:18.786 And I told you the catalog wouldn't work without that.
01:38:19.316 --> 01:38:20.266 Yeah, we can try it.
01:38:21.566 --> 01:38:24.916 I'm also thinking that, uh, we just have that syntax wrong.
01:38:23.746 --> 01:38:26.176 Which could not be. Yeah. Yeah. OK.
01:38:24.916 --> 01:38:26.926 Like we just have the syntax wrong.
01:38:29.446 --> 01:38:30.536 And I've I've.
01:38:31.426 --> 01:38:34.387 Only managed to make sense of Kibana and make it work once, so
01:38:34.387 --> 01:38:36.456 I'm gonna see if I can figure it out again.
01:38:36.866 --> 01:38:39.637 Check out those queries that I sent. That should get you
01:38:37.556 --> 01:38:38.286 He puts upset.
01:38:39.456 --> 01:38:40.006 Yeah.
01:38:39.637 --> 01:38:40.026 started.
01:38:40.926 --> 01:38:41.256 OK.
01:38:41.386 --> 01:38:43.886 OK, so copy and paste this straight.
01:38:45.326 --> 01:38:48.891 Yeah, you can keep what you have in the console if you want and
01:38:48.891 --> 01:38:51.176 just comment it or put it in a new area.
01:38:51.856 --> 01:38:55.696 Let's say you have it but like put it in notepad or something.
01:38:56.736 --> 01:38:57.286 OK.
01:38:57.006 --> 01:39:01.466 Because once we get the once and I've got some other snippets we
01:39:01.466 --> 01:39:05.858 can use if we need to, but once you get the actual like listing
01:39:05.858 --> 01:39:06.476 of these.
01:39:07.306 --> 01:39:07.556 Cool.
01:39:08.576 --> 01:39:11.806 Yeah. And then you can.
01:39:12.726 --> 01:39:16.153 You can modify see how it has product search. It looks like
01:39:16.153 --> 01:39:18.096 based on what I was seeing there.
01:39:21.616 --> 01:39:22.986 Yeah, we're going to do job.
01:39:23.656 --> 01:39:25.326 Dash search for something.
01:39:23.696 --> 01:39:23.896 Yeah.
01:39:24.966 --> 01:39:25.406 Exactly.
01:39:25.546 --> 01:39:27.086 I only need one of these, right?
01:39:27.496 --> 01:39:28.876 You're gonna want both of those.
01:39:28.226 --> 01:39:28.716 Or no.
01:39:29.366 --> 01:39:31.786 Yeah. OK. So.
01:39:33.806 --> 01:39:35.996 At least it's so, yeah. So it's gonna be.
01:39:36.696 --> 01:39:37.286 Ohh.
01:39:37.476 --> 01:39:38.826 Job instead of product.
01:39:39.166 --> 01:39:41.721 Yeah, I think that's only difference is just there might
01:39:39.956 --> 01:39:40.416 Yeah.
01:39:41.721 --> 01:39:44.276 be job opening. Check the app settings again to confirm.
01:39:43.796 --> 01:39:48.281 It's job. Yeah, it's job and then the regex star. The takes
01:39:46.456 --> 01:39:46.786 OK.
01:39:48.281 --> 01:39:50.076 care of the rest, right?
01:39:50.606 --> 01:39:51.506 It should, yeah.
01:39:51.556 --> 01:39:52.096 Yes, Sir.
01:39:52.576 --> 01:39:53.566 Wild card.
01:39:54.886 --> 01:39:57.506 And then so that one.
01:40:02.416 --> 01:40:02.846 So that.
01:40:03.496 --> 01:40:03.696 Hmm.
01:40:03.716 --> 01:40:04.366 Mean anything?
01:40:04.876 --> 01:40:08.443 It almost looks like there's the like highlight all of it and run
01:40:08.443 --> 01:40:08.606 it.
01:40:14.416 --> 01:40:17.366 But the other one, yeah, hit that, hit the yeah.
01:40:14.796 --> 01:40:16.506 Yeah, like control a.
01:40:18.776 --> 01:40:20.826 Yeah, it almost looks like it's not getting anything.
01:40:19.586 --> 01:40:21.416 It's like it didn't find anything. Yeah.
01:40:22.046 --> 01:40:23.656 What is the name of the thing?
01:40:26.656 --> 01:40:30.593 Should be job job, dash search, dash, Tsao, Dash, local, open up
01:40:26.776 --> 01:40:27.786 In the settings.
01:40:26.906 --> 01:40:27.816 The.
01:40:30.593 --> 01:40:33.986 your app settings again. Just eyeball it and make sure.
01:40:32.686 --> 01:40:33.166 Yeah.
01:40:35.176 --> 01:40:35.706 Yeah.
01:40:36.686 --> 01:40:39.516 We can try the job resume search index one as well.
01:40:46.216 --> 01:40:48.946 Yeah, I mean, you could just make it job, star.
01:40:48.676 --> 01:40:51.356 Yeah, job star that that probably be smarter, yeah.
01:40:49.896 --> 01:40:51.196 Yeah, yeah.
01:40:53.076 --> 01:40:55.583 It's gotta be. It's gotta be something with job in it. You
01:40:55.583 --> 01:40:56.476 would you would hope.
01:41:05.376 --> 01:41:06.926 Nothing, right?
01:41:06.986 --> 01:41:07.256 Hmm.
01:41:07.386 --> 01:41:10.897 And maybe put an explicit setting in your elastic search
01:41:08.036 --> 01:41:09.346 What if we removed?
01:41:10.897 --> 01:41:12.006 so we know you're.
01:41:12.656 --> 01:41:15.570 Calling to your local. Are you sure the default goes to local?
01:41:15.570 --> 01:41:18.531 I thought the default might have been changed to go to like our
01:41:18.531 --> 01:41:19.086 network one.
01:41:19.966 --> 01:41:23.271 Let me check to be sure, but I think it still goes to local by
01:41:22.856 --> 01:41:24.696 The default so logo OK.
01:41:23.271 --> 01:41:26.576 default. I could be wrong. We I I don't remember if we changed
01:41:26.576 --> 01:41:27.206 that or not.
01:41:28.246 --> 01:41:31.926 Let's see here config connection.
01:41:34.526 --> 01:41:37.326 Yeah. At least that's on developer me. Make sure that.
01:41:38.726 --> 01:41:43.761 That way on Tesco's? Well, yeah, looks like the default is still
01:41:43.761 --> 01:41:48.486 local host port #9200, so that should be. That should be OK.
01:41:50.006 --> 01:41:53.526 Maybe just make it star and see if you get anything.
01:41:51.946 --> 01:41:54.265 Yeah, that's what I was. That's what I was gonna say. See if it
01:41:54.265 --> 01:41:55.026 gets anything at all.
01:41:55.496 --> 01:41:55.886 Yeah.
01:41:56.066 --> 01:41:56.756 Excuse me.
01:42:09.376 --> 01:42:09.636 You know.
01:42:10.826 --> 01:42:11.686 And there's something.
01:42:11.776 --> 01:42:12.166 So.
01:42:13.426 --> 01:42:17.088 So it's not indexing anything at all. So how's it getting results
01:42:17.088 --> 01:42:17.366 then?
01:42:20.396 --> 01:42:21.106 That is.
01:42:22.536 --> 01:42:23.246 Strange.
01:42:25.436 --> 01:42:28.621 Was that maybe what you would index previously and it's just
01:42:28.621 --> 01:42:31.545 referencing that because it looks like it's not getting
01:42:31.545 --> 01:42:31.806 into.
01:42:31.796 --> 01:42:36.128 Yeah, it's not. Nothing's cashed for Tasco at all. You're develop
01:42:36.128 --> 01:42:36.916 locals here.
01:42:37.946 --> 01:42:39.006 But nothing else.
01:42:43.206 --> 01:42:43.736 Ohh.
01:42:50.076 --> 01:42:52.166 Whenever you manually end at oh, you got it.
01:42:50.246 --> 01:42:50.586 OK.
01:42:52.676 --> 01:42:53.216 Doesn't say.
01:42:54.896 --> 01:42:58.501 Let's let's actually let's attach to the admin app pool.
01:42:58.501 --> 01:43:02.612 When we run the index and see if it's giving us like an error or
01:43:02.612 --> 01:43:06.470 something. Maybe it's like just full on failing to index and
01:43:06.470 --> 01:43:10.518 somehow we're getting products or job openings. Anyway, there's
01:43:10.518 --> 01:43:14.123 something that's like making sure it always returns some
01:43:14.123 --> 01:43:14.566 values.
01:43:15.626 --> 01:43:18.846 Umm, but that would potentially explain some of the broken
01:43:18.846 --> 01:43:22.176 filtering too if if elastic doesn't have any data to filter.
01:43:30.006 --> 01:43:33.026 We're gonna set up. I gotta set a break point, no.
01:43:34.406 --> 01:43:37.271 Well, the good news is, is uh, well, let's check your exception
01:43:37.271 --> 01:43:40.001 settings real quick. So bottom kind of right of center. Yep.
01:43:40.001 --> 01:43:42.822 OK, we're good. So good news is you were attached when you did
01:43:40.976 --> 01:43:41.296 Yeah.
01:43:42.822 --> 01:43:45.373 that. It didn't throw any exceptions. So that's good. Or
01:43:45.373 --> 01:43:47.836 we would have, we would have stopped on the exception.
01:43:48.566 --> 01:43:50.556 So in the in the dump reader.
01:43:48.656 --> 01:43:49.096 Right.
01:43:51.206 --> 01:43:54.276 And actually, let's do the the indexer.
01:43:55.996 --> 01:43:59.868 Uh, yeah. And then it's gonna. It's derived from indexer base.
01:43:59.868 --> 01:44:01.466 So up a little bit higher.
01:44:04.946 --> 01:44:08.616 Yeah, right there. Online 15 F 12 into that indexer base.
01:44:11.766 --> 01:44:14.926 OK. And then put a break point on line 74.
01:44:18.476 --> 01:44:20.226 Perfect. All right, now let's run it.
01:44:24.626 --> 01:44:27.326 OK, so let's step through here, see.
01:44:37.196 --> 01:44:37.616 You know.
01:44:41.076 --> 01:44:43.696 Let's just contact profile names, all tests.
01:44:45.036 --> 01:44:47.696 So it did not fail on that first possible failure.
01:44:48.826 --> 01:44:49.896 OK, step over.
01:44:49.186 --> 01:44:52.576 So there's the actual index search name, right?
01:44:52.636 --> 01:44:55.937 Yeah. So it is doing job dash search, which is obviously not
01:44:55.676 --> 01:44:56.066 Yeah.
01:44:55.937 --> 01:44:58.806 successfully creating. So step over once right here.
01:45:00.996 --> 01:45:02.996 OK, it says that it created.
01:45:03.646 --> 01:45:06.814 The index just then at least that's what that method is
01:45:06.814 --> 01:45:10.096 called. So let's run back and run that star again on the.
01:45:11.636 --> 01:45:13.826 On Cuban and see if it shows anything right now.
01:45:18.696 --> 01:45:19.176 Also.
01:45:20.026 --> 01:45:21.256 Nope, same thing.
01:45:26.806 --> 01:45:27.036 Yeah.
01:45:28.426 --> 01:45:28.976 Umm.
01:45:34.176 --> 01:45:36.566 Alright, go back into uh Visual Studio.
01:45:38.046 --> 01:45:41.911 And drag the execution back up one line and then step in
01:45:41.911 --> 01:45:43.606 instead of stepping over.
01:45:46.276 --> 01:45:48.837 See if maybe there's like something in here. Alright, so
01:45:48.837 --> 01:45:49.916 let's walk through here.
01:45:55.536 --> 01:45:56.546 Just keep rolling.
01:46:00.706 --> 01:46:05.333 OK, so it does client dot create dot create index async with the
01:46:05.333 --> 01:46:06.116 index name.
01:46:08.246 --> 01:46:09.536 A mouse over client.
01:46:11.536 --> 01:46:13.246 And see expand it.
01:46:14.596 --> 01:46:15.576 Maybe it has like a.
01:46:17.776 --> 01:46:20.366 Connection settings that looks like a winner.
01:46:22.066 --> 01:46:23.496 Non public members.
01:46:28.356 --> 01:46:31.345 Scroll around, see if there's anything any of that tells us
01:46:31.345 --> 01:46:33.986 what it's what server it's connecting to, and stuff.
01:46:45.536 --> 01:46:48.026 Default index is fine, that doesn't matter too much.
01:46:49.176 --> 01:46:50.286 UM.
01:46:52.976 --> 01:46:56.740 Alright, so go back up and then there's like the HTTP connection
01:46:56.740 --> 01:47:00.214 at the very top. Let's expand that and see if it'll tell us
01:47:00.214 --> 01:47:00.736 the host.
01:47:03.656 --> 01:47:05.546 They're at their connection. It's like fourth down.
01:47:06.586 --> 01:47:07.616 Expand that one.
01:47:09.096 --> 01:47:09.576 OK.
01:47:11.106 --> 01:47:12.016 That's not what we wanted.
01:47:16.376 --> 01:47:18.614 It's gotta be something that tells us where this thing's
01:47:18.614 --> 01:47:19.086 pointing to.
01:47:23.066 --> 01:47:26.211 So as we could also look at how this client gets initialized,
01:47:26.211 --> 01:47:27.936 obviously gets created somewhere.
01:47:28.606 --> 01:47:29.176 Umm.
01:47:35.856 --> 01:47:38.556 OK click on client and then hit F-12.
01:47:43.776 --> 01:47:46.733 Ah, OK, let's go into that. Get client method and see what's
01:47:46.733 --> 01:47:47.606 going on in there.
01:47:51.686 --> 01:47:54.483 OK, generate connection settings. So what we got in
01:47:54.483 --> 01:47:54.806 there?
01:48:00.636 --> 01:48:04.356 OK, so pretty Jason glued and then debug mode.
01:48:07.486 --> 01:48:10.601 And then it sets up default mappings for all of our
01:48:10.601 --> 01:48:14.016 indexable models, with the default index names for them.
01:48:23.436 --> 01:48:24.396 OK. And then?
01:48:27.056 --> 01:48:29.972 Ohh create Uri up there at the top. That's where it's doing the
01:48:29.972 --> 01:48:30.246 thing.
01:48:31.776 --> 01:48:33.766 Create Uri on 33.
01:48:36.976 --> 01:48:37.966 See what that's doing?
01:48:46.556 --> 01:48:47.686 Do you have Fiddler running?
01:49:05.266 --> 01:49:06.816 Tim, if you're talking, I can't hear you.
01:49:11.276 --> 01:49:11.766 You're good.
01:49:11.826 --> 01:49:15.014 No, I I don't know. If I don't know what's fiddler, is it
01:49:15.014 --> 01:49:18.366 associated with elastic search like the install itself or is
01:49:18.366 --> 01:49:19.246 this a separate?
01:49:19.146 --> 01:49:21.251 It would be a separate tool if you don't know, you probably
01:49:21.251 --> 01:49:23.076 don't have it, but we could search just to be sure.
01:49:22.476 --> 01:49:22.916 Yeah.
01:49:24.536 --> 01:49:26.526 Just click here like Windows search and type fiddler.
01:49:27.696 --> 01:49:28.496 Yeah, I don't have.
01:49:27.856 --> 01:49:29.881 Yeah, OK. You don't have it installed. OK, so that's
01:49:29.881 --> 01:49:30.836 probably not the problem.
01:49:37.816 --> 01:49:39.966 Host gone port.
01:49:37.836 --> 01:49:39.216 For new host lists or.
01:49:41.906 --> 01:49:42.386 OK.
01:49:42.046 --> 01:49:42.856 I need 200.
01:49:44.546 --> 01:49:46.656 Yeah. OK, what about? Uh.
01:49:48.006 --> 01:49:51.596 Elastic surging Uri on line 117.
01:49:53.426 --> 01:49:56.656 So it's six searching here on your here.
01:49:57.196 --> 01:50:00.456 OK, it's all closed. Yeah. And the value that it read out was a
01:49:59.716 --> 01:49:59.986 Yep.
01:50:00.456 --> 01:50:03.666 close. OK, so it's definitely trying to connect to your local.
01:50:06.236 --> 01:50:07.376 So why?
01:50:10.626 --> 01:50:11.336 My.
01:50:11.996 --> 01:50:13.356 Would it do that?
01:50:26.666 --> 01:50:27.206 Umm.
01:50:31.196 --> 01:50:34.376 Is this Kibana instance pointed to a different instance of?
01:50:38.276 --> 01:50:42.107 Which McCall? It lastic Serge. Probably under management. Let's
01:50:42.107 --> 01:50:42.766 check that.
01:50:47.336 --> 01:50:49.046 Advanced settings perhaps?
01:50:52.976 --> 01:50:55.106 Caution, you can break stuff here. Nice.
01:51:01.596 --> 01:51:03.136 I don't see anything in here.
01:51:08.156 --> 01:51:10.126 There's nothing related to the connection stuff.
01:51:15.296 --> 01:51:17.286 Click the discover one in the top left.
01:51:41.426 --> 01:51:44.126 Configure a default index pattern.
01:51:44.646 --> 01:51:47.402 In order to use Kabani misconfigured at least one index
01:51:47.402 --> 01:51:47.796 pattern.
01:51:50.006 --> 01:51:54.546 Uh, OK, I guess type product, dash search dash *.
01:52:02.126 --> 01:52:02.586 OK.
01:52:03.916 --> 01:52:06.233 This seems like it's not complaining anymore. I go back
01:52:06.233 --> 01:52:07.226 to the Discover tab now.
01:52:11.266 --> 01:52:13.506 And that's and it reset it back to what it was before.
01:52:14.276 --> 01:52:15.176 OK, well.
01:52:15.966 --> 01:52:16.656 That's annoying.
01:52:18.216 --> 01:52:18.996 Uh.
01:52:27.736 --> 01:52:29.466 Those are both deprecated like that.
01:52:30.716 --> 01:52:33.426 So I got it do something to.
01:52:32.256 --> 01:52:32.936 I don't know.
01:52:44.246 --> 01:52:46.872 And you click away from it. Now if you try to go somewhere else,
01:52:46.872 --> 01:52:47.196 does it.
01:52:48.016 --> 01:52:50.961 Person of flames again. Yeah, just immediately breaks it. OK,
01:52:50.961 --> 01:52:53.621 now try to click discover when you're not on that index
01:52:53.621 --> 01:52:54.286 patterns page.
01:52:55.416 --> 01:52:56.016 Takes me there.
01:52:57.606 --> 01:52:58.186 Hey, there we go.
01:52:59.226 --> 01:52:59.676 What about?
01:53:00.106 --> 01:53:00.316 Right.
01:53:01.096 --> 01:53:03.146 Right, OK, I saw something else.
01:53:02.266 --> 01:53:03.736 They have tools, works.
01:53:04.646 --> 01:53:05.476 This works.
01:53:05.866 --> 01:53:09.359 What about discover from here on a page that works, it kicks you
01:53:09.359 --> 01:53:12.799 over there. Alright, well, let's just go back to Dev Tools then
01:53:09.936 --> 01:53:10.206 So.
01:53:12.799 --> 01:53:16.024 and run that command again. That we had. That was working a
01:53:16.024 --> 01:53:16.616 minute ago.
01:53:18.686 --> 01:53:19.876 See where we're at?
01:53:20.976 --> 01:53:21.986 That we still have nothing.
01:53:34.236 --> 01:53:36.326 There's a settings button, the very top right.
01:53:40.386 --> 01:53:41.026 That didn't help.
01:53:42.886 --> 01:53:45.783 It's like this is pointed at a difference of elastic itself,
01:53:45.783 --> 01:53:48.871 because nothing failed, but that creating that index and I'm I'm
01:53:48.871 --> 01:53:49.916 sure you've had other.
01:53:51.786 --> 01:53:53.666 Times that you've set up a.
01:53:54.486 --> 01:53:56.336 Yeah. So.
01:53:54.936 --> 01:53:58.416 Seth site. Besides, you're the first time you set up your
01:53:58.416 --> 01:53:59.916 develop local in October.
01:53:59.776 --> 01:54:04.292 This, but you might be you might be correct about that. OK,
01:54:04.292 --> 01:54:08.356 because I had an issues with. I had all three Kibana,
01:54:08.356 --> 01:54:11.066 Elasticsearch and Redis running in.
01:54:11.846 --> 01:54:16.395 No, this is I didn't move elastic surge out of I just
01:54:16.395 --> 01:54:17.996 moved Redis out of.
01:54:19.566 --> 01:54:22.566 Out of docker. Yeah. Yeah, so.
01:54:19.706 --> 01:54:25.466 Out of a docker. OK, so Docker is running for for elastic and
01:54:25.466 --> 01:54:27.046 Kibana right now.
01:54:26.216 --> 01:54:26.466 And.
01:54:27.846 --> 01:54:28.236 Yeah.
01:54:28.416 --> 01:54:28.976 OK.
01:54:31.326 --> 01:54:34.917 You should stop the cabana one that's running in, like,
01:54:34.917 --> 01:54:38.637 temporarily. Just stop this one cause we started a cabana
01:54:38.637 --> 01:54:40.176 instance by opening the.
01:54:41.096 --> 01:54:41.756 Or did we?
01:54:44.906 --> 01:54:47.963 If refresh that page, is it just not load anymore? I might be
01:54:47.963 --> 01:54:51.169 wrong. I thought I remembered we we manually started Kibana, but
01:54:51.169 --> 01:54:52.106 I'm probably wrong.
01:54:54.496 --> 01:54:54.906 Yeah.
01:55:13.296 --> 01:55:16.256 Here it's this flyer. Log out.
01:55:31.816 --> 01:55:34.726 So, OK, Ohh job seeker.
01:55:35.626 --> 01:55:36.406 Charlie.
01:55:54.276 --> 01:55:55.976 Success, great success.
01:56:00.536 --> 01:56:02.116 This is returning 27.
01:56:04.186 --> 01:56:05.246 Aunt Q, OK.
01:56:06.136 --> 01:56:06.446 Yeah.
01:56:08.046 --> 01:56:12.066 So it's something to do with my local, right?
01:56:13.676 --> 01:56:14.906 It would seem so.
01:56:21.636 --> 01:56:24.606 Likely you have one job that's the salary of five USD in
01:56:24.606 --> 01:56:26.586 another one, that's like 900 million.
01:56:27.966 --> 01:56:28.646 Yeah.
01:56:29.826 --> 01:56:32.076 So what is?
01:56:33.246 --> 01:56:35.356 Let's look at the UM, let's look at that.
01:56:36.836 --> 01:56:38.586 Link, he said with.
01:56:41.656 --> 01:56:44.036 Set up right like because obviously it's not.
01:56:44.846 --> 01:56:48.651 My cabana is not point is not something, right? Like it's not
01:56:48.651 --> 01:56:50.616 set up correctly or it can't be.
01:56:53.226 --> 01:56:54.956 Because the only thing shown in Kibana.
01:56:53.646 --> 01:56:57.225 I'm just trying to remember where where you even set that in
01:56:57.225 --> 01:56:57.636 Kibana.
01:57:00.786 --> 01:57:01.696 Browser.
01:57:01.216 --> 01:57:05.425 As my Discover tab works on my cabana locally, so I'm going to
01:57:05.425 --> 01:57:05.826 check.
01:57:07.086 --> 01:57:08.616 You go to your settings.
01:57:10.396 --> 01:57:13.663 Yeah, I'm in there and the management going to management,
01:57:13.663 --> 01:57:14.826 click index patterns.
01:57:17.166 --> 01:57:18.156 Just put star.
01:57:21.976 --> 01:57:24.246 And then time filter field name.
01:57:25.726 --> 01:57:29.886 Uh. Put, create. Uh, yeah, that works cool. OK.
01:57:31.216 --> 01:57:32.946 Neat. OK, now go to discover.
01:57:36.056 --> 01:57:38.546 Hey, all right, it didn't burst into flames this time.
01:57:40.186 --> 01:57:41.216 OK so.
01:57:52.696 --> 01:57:54.526 These are all the suggests, right?
01:57:55.156 --> 01:57:55.946 We should have.
01:57:55.206 --> 01:57:55.746 Yeah.
01:57:56.976 --> 01:57:57.806 And.
01:57:57.316 --> 01:57:59.376 We should have job stuff in here, right?
01:58:00.386 --> 01:58:03.466 You would think so. So go to the management one.
01:58:07.176 --> 01:58:08.346 Index patterns.
01:58:09.506 --> 01:58:14.456 Uh. And then in that star scroll through here and look for uh,
01:58:14.456 --> 01:58:17.836 title would be one that's specifically on.
01:58:18.906 --> 01:58:23.092 UM jobs, so scroll to the far like to the right until you see
01:58:23.092 --> 01:58:26.806 one that starts with like the the name would be title.
01:58:28.566 --> 01:58:29.906 Scroll through the far right.
01:58:30.056 --> 01:58:32.992 As in sorry, Scroll down and then keep uh clicking the, you
01:58:32.992 --> 01:58:35.146 know, next page button until you get there.
01:58:34.326 --> 01:58:37.026 Can we can we search OK?
01:58:36.576 --> 01:58:38.416 As you probably could, yeah, yeah.
01:58:39.006 --> 01:58:40.756 By title everything.
01:58:40.276 --> 01:58:40.716 Yeah.
01:58:42.256 --> 01:58:44.296 Title string OK.
01:58:42.306 --> 01:58:42.776 Title.
01:58:47.966 --> 01:58:48.656 Interesting.
01:58:49.756 --> 01:58:50.236 Yeah.
01:58:52.476 --> 01:58:53.126 Alright.
01:59:00.556 --> 01:59:01.306 There should have been a.
01:59:03.226 --> 01:59:04.576 A company name 1, right?
01:59:10.026 --> 01:59:11.196 Yeah, I think so.
01:59:19.306 --> 01:59:20.026 On time.
01:59:20.926 --> 01:59:23.806 Go to the dev tools and type.
01:59:26.206 --> 01:59:27.186 Uh, get.
01:59:29.546 --> 01:59:30.806 Let's just do like a new line.
01:59:31.526 --> 01:59:31.786 Yeah.
01:59:31.566 --> 01:59:32.336 At the bottom.
01:59:33.346 --> 01:59:36.555 And then get in all caps and then job search task go local
01:59:36.555 --> 01:59:39.709 just like it is in your no no forward slash. This is what
01:59:39.709 --> 01:59:42.918 actually happened in mind. Apparently I had this open from
01:59:42.918 --> 01:59:45.366 the last time I actually got cabana working.
01:59:46.116 --> 01:59:49.056 Uh and then slash under score search.
01:59:50.776 --> 01:59:54.523 OK. And then run that and see if we still get like a 404 or
01:59:54.523 --> 01:59:55.086 whatever?
01:59:57.606 --> 02:00:01.177 Index not found. OK, so it it just doesn't know what we mean.
02:00:01.177 --> 02:00:04.691 I'm almost certain that this cabana, since it's just pointed
02:00:04.691 --> 02:00:05.786 to the wrong place.
02:00:06.606 --> 02:00:07.466 But I don't know how to.
02:00:10.646 --> 02:00:11.636 I don't know how to fix that.
02:00:20.226 --> 02:00:21.406 Something, right?
02:00:22.586 --> 02:00:24.736 The job search one, not the job resume new one.
02:00:26.146 --> 02:00:26.616 Well.
02:00:26.486 --> 02:00:28.486 Unless you want to try the job, resume one but.
02:00:28.356 --> 02:00:29.436 Yeah, yeah, yeah.
02:00:31.516 --> 02:00:31.796 This.
02:00:35.336 --> 02:00:35.996 Yeah, nothing.
02:00:35.766 --> 02:00:40.972 Yeah. OK. Real quick, back in the the the stuff code, looking
02:00:40.972 --> 02:00:42.316 at the indexing.
02:00:43.066 --> 02:00:47.251 Odjick were looking at earlier so indexer base. So if 12-1 and
02:00:47.251 --> 02:00:47.916 this file.
02:00:51.326 --> 02:00:56.267 OK, looking at scroll a little bit more, this index control or
02:00:56.267 --> 02:01:00.346 go into that create index async again F-12 on that.
02:01:05.136 --> 02:01:06.416 Alright, Scroll down.
02:01:16.146 --> 02:01:17.086 OK, that doesn't help me.
02:01:18.126 --> 02:01:18.826 Umm.
02:01:38.596 --> 02:01:42.506 Yeah, let's check that. Do the non public members.
02:01:44.846 --> 02:01:47.004 However, back to this. So what we're looking at earlier, never
02:01:47.004 --> 02:01:47.176 mind.
02:01:47.686 --> 02:01:48.076 Same.
02:01:48.976 --> 02:01:51.342 Yeah, alright, that's fine. We already confirmed that it's
02:01:49.796 --> 02:01:50.246 And this.
02:01:51.342 --> 02:01:52.786 loading the right connection stuff.
02:01:53.796 --> 02:01:54.476 Yeah.
02:01:53.906 --> 02:01:57.104 But there's something I wanted to look at in here. Go back to
02:01:57.104 --> 02:01:57.826 where we were.
02:02:00.006 --> 02:02:03.206 And then F-12 and two swap alias async.
02:02:09.586 --> 02:02:12.876 OK, break point on 2:30 and then just hit continue.
02:02:14.406 --> 02:02:18.479 Because this has a, this has a thing that says to check if the
02:02:18.479 --> 02:02:22.228 index exists, and we can so type get live index name from
02:02:22.228 --> 02:02:26.366 settings. So if you like online 232 you can copy it from there.
02:02:27.526 --> 02:02:30.726 Uh, get live index name from setting that whole method copy
02:02:30.726 --> 02:02:33.712 that call including the parentheses to run it, and then
02:02:33.712 --> 02:02:36.646 put that in the watch and let's see what it spits out.
02:02:40.196 --> 02:02:43.304 Chapter test global. OK, that's what I figured. Alright, so
02:02:43.304 --> 02:02:46.464 let's step down to line 233 and see if that returns true. If
02:02:46.464 --> 02:02:49.572 that returns true, then we can guarantee that Kibana is not
02:02:49.572 --> 02:02:52.266 showing anything because it's pointed at the wrong.
02:02:53.866 --> 02:02:55.116 Elasticsearch instance.
02:02:56.626 --> 02:02:57.786 So step one more.
02:02:56.966 --> 02:02:58.946 OK, step one more.
02:03:00.046 --> 02:03:03.385 OK. And then check it is OK index exists alright, so the the
02:03:03.385 --> 02:03:06.616 cabana one just pointed at something else. Who knows what?
02:03:10.276 --> 02:03:11.626 That's that's fine.
02:03:11.946 --> 02:03:16.151 Umm, but it did indeed find it. It's going to create an alias
02:03:16.151 --> 02:03:16.626 for it.
02:03:22.946 --> 02:03:23.876 Which is fine.
02:03:32.686 --> 02:03:33.126 Stephen.
02:03:34.006 --> 02:03:35.296 Yeah, go ahead and step over.
02:03:37.816 --> 02:03:41.506 It induces pointing to alias OK, step over once.
02:03:43.546 --> 02:03:45.576 And then how does that have in it?
02:03:46.666 --> 02:03:47.716 Results for you.
02:03:49.736 --> 02:03:53.879 One thing, OK, so it it did indeed find the old index. So
02:03:53.879 --> 02:03:56.736 all these indices exist, it's just not.
02:03:57.966 --> 02:04:01.365 The the Kibana instances pointed at something else and I'm I'm
02:04:01.365 --> 02:04:04.765 betting that the issue you're having with not seeing the stuff
02:04:04.765 --> 02:04:08.057 in Kibana is that it's running in a Docker container and the
02:04:08.057 --> 02:04:09.676 whole point of the containers.
02:04:10.496 --> 02:04:14.457 Is that they can't, like they're they don't talk to each other.
02:04:12.836 --> 02:04:15.529 They're. Yeah, they're containerized, right? Yeah.
02:04:14.457 --> 02:04:16.686 Yeah, they're isolated. Yeah. Yeah.
02:04:15.529 --> 02:04:17.906 They're on their own network and everything.
02:04:17.936 --> 02:04:21.577 Yeah. So I'm guessing that the cabana instance is probably
02:04:21.577 --> 02:04:25.526 trying to talk to Elasticsearch inside its own container, which
02:04:25.526 --> 02:04:29.167 it's not in its own container. They're running in separate
02:04:29.167 --> 02:04:29.846 containers.
02:04:30.446 --> 02:04:32.916 And thus it is 2 completely separate things so.
02:04:34.836 --> 02:04:38.162 Umm, so that's probably what's going on there. You could
02:04:38.162 --> 02:04:42.013 probably download the old cabana thing and run it locally instead
02:04:42.013 --> 02:04:43.706 of running it through Docker.
02:04:46.136 --> 02:04:48.028 I'd probably still have a download link for that
02:04:48.028 --> 02:04:49.496 somewhere. Let me find it real quick.
02:04:53.536 --> 02:04:56.894 But that would help us actually get visibility on this. It's a
02:04:56.894 --> 02:05:00.146 lot harder to excuse me, lot harder to tell what's going on.
02:05:01.786 --> 02:05:02.226 Yeah.
02:05:01.786 --> 02:05:04.056 Uh, when we can't see the data?
02:05:05.386 --> 02:05:08.530 Which is kind of that's always the issue with the lastic
02:05:08.530 --> 02:05:11.840 searches that it's kind of a black box, very hard for us to
02:05:11.840 --> 02:05:12.116 tell.
02:05:12.836 --> 02:05:13.986 What's going on in there?
02:05:15.206 --> 02:05:17.316 You just change a bunch of dials and.
02:05:18.746 --> 02:05:19.376 Hope that it.
02:05:20.386 --> 02:05:23.023 That it produces something you want and not something you
02:05:23.023 --> 02:05:23.296 don't.
02:05:27.796 --> 02:05:31.486 I'm looking for, I think it was in the CEF team files.
02:05:39.346 --> 02:05:42.126 Yeah, OK, here we go. Copy link.
02:05:47.806 --> 02:05:51.228 OK, I just sent a link to it in the chat. Let me know if it
02:05:51.228 --> 02:05:52.826 doesn't let you download it.
02:05:57.696 --> 02:05:58.906 Wait, no, that's wrong.
02:06:01.966 --> 02:06:02.476 No.
02:06:05.426 --> 02:06:06.346 Download.
02:06:10.666 --> 02:06:13.216 Ohh yeah, I forgot. Yeah it's there.
02:06:13.866 --> 02:06:14.216 OK.
02:06:14.606 --> 02:06:16.326 So downloads.
02:06:15.796 --> 02:06:18.226 Yeah, just gotta wait for it to be done. It's a pretty big file.
02:06:19.386 --> 02:06:20.036 Yeah.
02:06:21.266 --> 02:06:24.316 Uh, wait once a second. So one extra.
02:06:22.976 --> 02:06:26.012 Just wait for it to wait for it to pop up. Just wait for it to
02:06:26.012 --> 02:06:29.146 pop up and tell you that it's a done installing, and then we'll.
02:06:29.916 --> 02:06:33.062 Be good in this case, all you'll need to do is extract the cabana
02:06:33.062 --> 02:06:35.827 folders. Since you already have elastic search set up and
02:06:35.827 --> 02:06:38.926 running in the Docker container, we'll just extract cabana into.
02:06:39.996 --> 02:06:40.586 Umm.
02:06:42.366 --> 02:06:45.084 It's still, I think it's still downloading. Do a refresh in
02:06:42.616 --> 02:06:43.346 So.
02:06:45.084 --> 02:06:47.486 here because it's definitely more than 19 megabytes.
02:06:48.596 --> 02:06:49.826 Ohh OK.
02:06:49.186 --> 02:06:49.526 Yeah.
02:06:51.416 --> 02:06:52.886 Let's go to a little bit too, uh.
02:06:51.446 --> 02:06:56.051 And get rid of that one. Ohly. Yeah, I gotta wait till it's
02:06:55.326 --> 02:06:57.116 Yeah, just let it just let it do its doing it.
02:06:56.051 --> 02:06:56.896 downloaded.
02:06:57.876 --> 02:07:01.442 It'll take it a bit to to catch up with us, but it's not too
02:07:01.442 --> 02:07:01.676 bad.
02:07:04.146 --> 02:07:06.766 So we're going to, I probably already got this, man.
02:07:08.126 --> 02:07:11.493 I didn't look like it would have the like the two in the file
02:07:11.493 --> 02:07:14.861 name instead of this being flat named and then one called one
02:07:13.536 --> 02:07:14.026 Well.
02:07:14.861 --> 02:07:16.056 unless you renamed it.
02:07:15.316 --> 02:07:18.616 Yeah, but it's not my down. Well, I probably moved. It would
02:07:18.616 --> 02:07:19.266 be my guess.
02:07:18.846 --> 02:07:20.326 Oh, OK. Yeah, that makes sense.
02:07:20.866 --> 02:07:22.516 Yeah. So.
02:07:23.196 --> 02:07:26.559 If you have it, I would save us some time because this zip file
02:07:23.846 --> 02:07:25.036 Probably my clarity.
02:07:26.559 --> 02:07:27.716 is like 400 megabytes.
02:07:30.086 --> 02:07:30.666 Yeah.
02:07:31.576 --> 02:07:34.226 Looking for to think go where I would have put.
02:07:31.886 --> 02:07:32.196 OK.
02:07:38.856 --> 02:07:40.166 I have a I have a tool.
02:07:39.326 --> 02:07:41.596 Could be data tools maybe? Yeah.
02:07:43.516 --> 02:07:44.426 Plastic search.
02:07:44.786 --> 02:07:46.146 Hey there it is.
02:07:46.476 --> 02:07:47.456 There's cabana.
02:07:46.856 --> 02:07:47.356 Nice.
02:07:48.836 --> 02:07:53.044 OK, so let's open up the UM, let's open the Elasticsearch 7
02:07:53.044 --> 02:07:53.746 zip first.
02:07:54.516 --> 02:07:58.914 And then inside of that, let's reextract that comma just to
02:07:58.914 --> 02:08:03.533 make sure that we have, you know it's all good or just open it
02:08:03.533 --> 02:08:04.486 that ideally.
02:08:05.526 --> 02:08:08.700 OK, now copy that Kibana folder just straight out into the stuff
02:08:08.700 --> 02:08:10.946 tools folder. You just click and drag it out.
02:08:13.576 --> 02:08:15.846 Yeah. OK. Let it do all the.
02:08:16.656 --> 02:08:18.866 Extract to flying that it needs to do.
02:08:20.916 --> 02:08:23.930 Yeah, that download was going so slow, probably because I'm on a
02:08:23.930 --> 02:08:26.898 hotspot. They've been working on my Internet since like 1:00 PM
02:08:26.898 --> 02:08:29.680 yesterday, like an outage in the area because the guy hit a
02:08:26.986 --> 02:08:27.766 Ohh jeez.
02:08:29.680 --> 02:08:30.376 telephone pole.
02:08:30.446 --> 02:08:32.927 Ohh that's right, I saw you posted about that. Yeah, that's
02:08:32.236 --> 02:08:32.906 Yeah.
02:08:32.927 --> 02:08:33.176 crazy.
02:08:33.756 --> 02:08:37.119 Yeah. Well, at first it was just the electric was out, right. And
02:08:37.119 --> 02:08:39.616 then, like, the Internet went out shortly after.
02:08:40.386 --> 02:08:42.956 Uh, they got the electric back on the Internet, went out.
02:08:46.226 --> 02:08:47.726 So here we are in Kibana.
02:08:48.146 --> 02:08:52.142 OK. In the bin folder, there's a cabana dot bat. Before you run
02:08:52.142 --> 02:08:55.576 that, let's stop the service running Kibana in Docker.
02:08:58.066 --> 02:08:58.466 Yeah.
02:08:58.326 --> 02:09:00.976 Perfect. OK. And then double click that bat file.
02:09:02.376 --> 02:09:03.786 And.
02:09:05.866 --> 02:09:06.976 Wait patiently.
02:09:10.126 --> 02:09:11.406 54321 go.
02:09:22.996 --> 02:09:26.986 Everything that I've went to do in this on Tasco has been.
02:09:24.566 --> 02:09:26.756 Status changed to green.
02:09:28.926 --> 02:09:29.696 Nightmarish.
02:09:31.556 --> 02:09:32.126 Yeah, man.
02:09:33.596 --> 02:09:34.056 Yeah.
02:09:33.706 --> 02:09:36.439 It looks like we're ready. Should be able to just go in and
02:09:36.439 --> 02:09:39.219 refresh that. Uh, keep on a page that we were on already and
02:09:39.219 --> 02:09:39.766 it'll be on.
02:09:41.136 --> 02:09:45.126 A different Kibana instance probably. OK, now run that first
02:09:45.126 --> 02:09:46.696 one and see what we get.
02:09:47.436 --> 02:09:48.166 Ohh.
02:09:48.646 --> 02:09:50.676 Yeah, that looks better. OK.
02:09:50.036 --> 02:09:52.506 There's a few more projects, yeah.
02:09:52.006 --> 02:09:56.292 Yeah, OK, let's run that, that that bottom line there, the job
02:09:55.816 --> 02:09:56.826 There's task.
02:09:56.292 --> 02:09:59.626 search test, go, local slash under score search.
02:10:03.416 --> 02:10:07.542 Total 23 so its indexing everything. The problem is our
02:10:07.542 --> 02:10:09.016 query, our query is.
02:10:10.426 --> 02:10:13.316 Predisposed to breaking things, it seems.
02:10:16.476 --> 02:10:18.086 But that's very cool.
02:10:19.286 --> 02:10:20.076 That.
02:10:22.936 --> 02:10:24.026 Yeah. So.
02:10:24.566 --> 02:10:27.844 OK, so we got this. We're seeing that we definitely did
02:10:27.844 --> 02:10:28.956 successfully index.
02:10:29.846 --> 02:10:32.036 All 23 things we expected to.
02:10:30.066 --> 02:10:30.716 The jobs.
02:10:32.726 --> 02:10:35.275 So now we definitely know the problem is something about the
02:10:33.006 --> 02:10:33.366 Yeah.
02:10:35.275 --> 02:10:35.526 query.
02:10:37.076 --> 02:10:37.546 OK.
02:10:38.806 --> 02:10:40.466 So I can detach from the.
02:10:41.336 --> 02:10:44.041 The add menu? Yeah, because we know that there's definitely not
02:10:41.596 --> 02:10:42.106 Admin.
02:10:43.216 --> 02:10:43.846 Yeah.
02:10:44.041 --> 02:10:44.676 an issue there.
02:10:45.776 --> 02:10:48.386 Attached back to the store front right.
02:10:49.786 --> 02:10:50.706 Or no.
02:10:54.116 --> 02:10:54.706 Yes.
02:10:56.766 --> 02:10:57.876 Yes indeedy.
02:11:10.026 --> 02:11:13.649 We probably got breakpoints still said. Well, I guess it
02:11:13.649 --> 02:11:15.556 won't matter on the admin but.
02:11:16.876 --> 02:11:19.966 So we need to go to the search mode. Uh is it?
02:11:20.726 --> 02:11:21.136 Yes.
02:11:21.756 --> 02:11:24.216 Though it's in the, we need to go back to the.
02:11:40.016 --> 02:11:42.756 We think go go back to dump reader.
02:11:49.136 --> 02:11:52.518 Let's let's start at the query and work our way through to
02:11:52.518 --> 02:11:55.785 where it actually builds it and see everything that gets
02:11:55.785 --> 02:11:57.906 applied. So go to the search module.
02:12:00.376 --> 02:12:05.000 Umm, scroll up, actually scroll. Yeah right there. Query that
02:12:05.000 --> 02:12:09.326 that method that we were looking at line 48 click on the.
02:12:09.206 --> 02:12:09.576 Ohh.
02:12:10.746 --> 02:12:13.569 Yeah, we wanna see where it's actually getting called. So
02:12:13.569 --> 02:12:15.516 right click and do find all references.
02:12:16.226 --> 02:12:18.266 Or you can do the two references right there. That works too.
02:12:19.286 --> 02:12:21.016 And click on that first one.
02:12:23.656 --> 02:12:27.473 OK, so this is where we actually build the query. So let's put a
02:12:27.473 --> 02:12:31.290 breakpoint on 37 and then go to the catalog or it will empty the
02:12:31.290 --> 02:12:31.936 Reus cache.
02:12:33.236 --> 02:12:33.906 And.
02:12:37.476 --> 02:12:39.756 And then check out the catalog and see what we get.
02:12:51.076 --> 02:12:54.636 I noticed that it seems like the browser thinks the page is
02:12:54.636 --> 02:12:55.526 always loading.
02:12:56.446 --> 02:12:57.216 Yeah, I know.
02:12:58.496 --> 02:13:01.679 I don't know what the deal is with that, even after all these
02:13:01.679 --> 02:13:02.296 complete my.
02:13:03.926 --> 02:13:06.136 Yeah, OK. I don't know.
02:13:04.966 --> 02:13:06.466 OK, well something.
02:13:07.566 --> 02:13:10.591 It's spinning up probably. Oh, we know we hit the breakpoint.
02:13:08.476 --> 02:13:11.716 Ohh, we're we're we're, huh? Yeah.
02:13:10.591 --> 02:13:12.006 Duh. Yeah, that thing we did.
02:13:13.026 --> 02:13:15.146 Yeah. OK.
02:13:14.026 --> 02:13:14.946 OK so.
02:13:15.716 --> 02:13:18.726 Uh, alright, so let's step over. Step over.
02:13:20.256 --> 02:13:23.662 One more time. OK, so this is where we actually build our
02:13:23.662 --> 02:13:26.892 query. So before we step anywhere, mouse over form dot
02:13:26.892 --> 02:13:27.186 page.
02:13:27.876 --> 02:13:28.916 On line 42.
02:13:31.866 --> 02:13:34.416 Pages one page size should be 9.
02:13:35.836 --> 02:13:37.586 Based on what it shows in the catalog.
02:13:38.886 --> 02:13:39.576 1000.
02:13:38.976 --> 02:13:42.087 Oh, this is the this is the last modified. Just hit continue for
02:13:42.087 --> 02:13:44.910 now, and then we'll hit this breakpoint a second time here
02:13:44.910 --> 02:13:47.256 and just a SEC. OK. Now let's step through here.
02:13:48.796 --> 02:13:49.216 OK.
02:13:51.836 --> 02:13:55.641 OK, yeah. Now don't step over yet, but page site pages. One
02:13:55.641 --> 02:13:59.066 page site should be not it's. Why is it still 10,000?
02:13:59.296 --> 02:14:00.126 Interesting.
02:14:01.636 --> 02:14:03.586 I thought maybe it said 10,000 million.
02:14:01.946 --> 02:14:02.286 Huh.
02:14:04.556 --> 02:14:06.176 It did say 10,000 last time.
02:14:07.206 --> 02:14:07.816 OK.
02:14:07.916 --> 02:14:09.206 Continue one more time.
02:14:12.576 --> 02:14:16.366 OK, we're back here again. Mouse over form dot page size.
02:14:17.276 --> 02:14:19.136 It's 10,000. Again, I'm going to lose my mind.
02:14:24.166 --> 02:14:26.936 On how OK, continue again.
02:14:26.306 --> 02:14:29.486 How have we hit this? Why are we hitting this over and over?
02:14:30.456 --> 02:14:34.233 That's that's part of my concern, right? What about now?
02:14:34.233 --> 02:14:34.896 Page size.
02:14:37.906 --> 02:14:39.296 And that OK continue again.
02:14:42.486 --> 02:14:43.436 We're back here again.
02:14:45.066 --> 02:14:45.986 Alright, what about now?
02:14:50.256 --> 02:14:52.346 I guess I could check it without stepping 10,000.
02:14:51.896 --> 02:14:53.826 Yeah. OK. Continue again.
02:14:55.676 --> 02:14:56.486 Continue again.
02:15:00.636 --> 02:15:04.471 We're back here again. What about still 10,000? OK, how
02:15:01.446 --> 02:15:02.076 10,000.
02:15:04.471 --> 02:15:05.156 about now?
02:15:06.846 --> 02:15:07.326 Alright.
02:15:10.376 --> 02:15:11.626 Alright, continue.
02:15:14.676 --> 02:15:17.176 It's like we're in a freaking loop.
02:15:19.926 --> 02:15:24.348 Kidding. There we go. OK, now it's actually. Yeah, that's
02:15:21.136 --> 02:15:21.986 Hey size 9.
02:15:22.896 --> 02:15:24.236 That was like 10 times.
02:15:24.348 --> 02:15:28.389 that's an indicator of that. Either the front end is
02:15:28.389 --> 02:15:33.117 repeatedly sending the query on page load, which is not great
02:15:33.117 --> 02:15:33.346 or.
02:15:35.316 --> 02:15:39.021 The back end has some kind of loop. It's getting stuck in
02:15:39.021 --> 02:15:42.855 where it's repeatedly running that is that page size 10,000
02:15:42.855 --> 02:15:43.686 that happens.
02:15:43.806 --> 02:15:46.976 Umm, the first thing that the.
02:15:48.336 --> 02:15:51.282 Provider does to try to determine if the caching. Yeah,
02:15:49.236 --> 02:15:50.006 304.
02:15:51.282 --> 02:15:54.597 it does a three or four stuff that we talked about a few weeks
02:15:54.406 --> 02:15:54.826 Yeah.
02:15:54.597 --> 02:15:57.806 ago and the way that it does that for elastic is it sets the
02:15:57.806 --> 02:16:00.963 page size to 10,000 to determine if any of the results have
02:16:00.963 --> 02:16:04.172 changed and if they have, then it would invalidate what's in
02:16:01.986 --> 02:16:02.336 Umm.
02:16:04.172 --> 02:16:07.329 the cache. So the fact that it hit that so many times means
02:16:07.329 --> 02:16:10.538 that there's probably an issue with that logic or there's an
02:16:10.538 --> 02:16:13.853 issue on the front end that's making it send this request like
02:16:13.853 --> 02:16:17.115 10 times on the page loads. But we should now be able to step
02:16:17.115 --> 02:16:17.536 through.
02:16:23.346 --> 02:16:26.826 And sanity check the rest of this stuff. Alright, so let's
02:16:26.826 --> 02:16:27.416 wait here.
02:16:29.166 --> 02:16:31.876 So page size 9 page should be one.
02:16:33.566 --> 02:16:37.743 OK, so all the pagination stuff looks correct now. What about
02:16:33.616 --> 02:16:33.906 Uh.
02:16:37.743 --> 02:16:38.956 SSO? What does SO?
02:16:40.206 --> 02:16:41.516 Ah, that's the sort thing, OK.
02:16:41.986 --> 02:16:42.216 Yeah.
02:16:43.516 --> 02:16:47.526 OK. So then what about form dot sort? If you mouse over that?
02:16:49.646 --> 02:16:53.592 Umm, just just mouse over form and then go into it and find uh
02:16:50.036 --> 02:16:50.666 Whereas.
02:16:53.592 --> 02:16:53.906 sort.
02:16:54.276 --> 02:16:54.716 Ohh.
02:16:55.106 --> 02:16:59.376 On the object. Yeah, should be a sort property somewhere.
02:17:01.146 --> 02:17:03.756 Yep. OK. So it's sort by recent alright, that's fine.
02:17:02.476 --> 02:17:02.816 Reason.
02:17:04.526 --> 02:17:05.056 Yeah.
02:17:06.836 --> 02:17:08.306 Step over I guess.
02:17:12.506 --> 02:17:15.489 And the only other thing I can think too is just sanity
02:17:15.489 --> 02:17:18.366 checking that our forms query isn't is null or empty.
02:17:21.626 --> 02:17:23.116 So like form query.
02:17:24.786 --> 02:17:27.636 It should be either null or an empty string.
02:17:29.576 --> 02:17:33.930 And it's null. OK, good. Alright, so then, now let's look
02:17:30.036 --> 02:17:30.406 No.
02:17:33.930 --> 02:17:34.606 at model.
02:17:35.496 --> 02:17:36.196 Umm.
02:17:37.056 --> 02:17:38.106 Or as our result.
02:17:43.356 --> 02:17:47.595 Yeah, let's see what's in here. Documents count equals 9, so it
02:17:47.595 --> 02:17:51.106 in fact did not get only eight things, but it got 9.
02:17:52.136 --> 02:17:54.646 OK, so if we Scroll down.
02:17:55.666 --> 02:18:00.176 This should tell us how many things it it hit in total.
02:18:01.756 --> 02:18:03.356 Total 23, OK.
02:18:04.306 --> 02:18:06.865 All right, so let's keep stepping through because this is
02:18:06.865 --> 02:18:08.896 starting to indicate to me that something is.
02:18:10.076 --> 02:18:13.856 Messing. Good. Just continue on this one. It's stepped back up
02:18:13.856 --> 02:18:15.416 to the top. OK, step over.
02:18:19.686 --> 02:18:22.096 OK, let's step over.
02:18:24.216 --> 02:18:26.326 What is API call if you mess over that?
02:18:28.306 --> 02:18:29.306 OK, that's fine.
02:18:30.266 --> 02:18:32.496 Uh, continue or not continue to step over.
02:18:36.686 --> 02:18:38.916 OK, keep going.
02:18:41.576 --> 02:18:42.726 Keep going.
02:18:44.976 --> 02:18:47.876 It is valid. That's good. So it means there was no error
02:18:47.876 --> 02:18:51.032 retrieving those search view model additional assignments. So
02:18:51.032 --> 02:18:52.406 step over and then step in.
02:18:58.166 --> 02:18:58.796 Continue.
02:19:00.636 --> 02:19:03.520 Actually we can remove that break point up there. I'm just
02:19:03.520 --> 02:19:04.596 so we stop hitting it.
02:19:05.586 --> 02:19:07.536 For now. OK, cool.
02:19:08.656 --> 02:19:09.166 Step in.
02:19:09.926 --> 02:19:10.536 Yes.
02:19:11.416 --> 02:19:13.626 We want to see make sure that this isn't.
02:19:14.536 --> 02:19:18.146 Listen, anything up? OK, step over and step in.
02:19:19.466 --> 02:19:22.200 So you want to step into that additional assignments for
02:19:22.200 --> 02:19:22.536 cities?
02:19:25.536 --> 02:19:26.166 OK.
02:19:27.156 --> 02:19:30.064 Yeah, OK. Doesn't look like it should mess anything up. Uh,
02:19:30.064 --> 02:19:31.276 step over. One step over.
02:19:34.536 --> 02:19:39.280 And then mouse over cities right there and see. OK, so found six
02:19:39.280 --> 02:19:43.586 unique cities, 1818 job entries have their city set to NA.
02:19:46.306 --> 02:19:49.263 And it says it's only one of them has its city set to Darien.
02:19:49.263 --> 02:19:50.026 Do you see that?
02:19:52.456 --> 02:19:54.426 If you mouse over cities again and.
02:19:52.796 --> 02:19:54.786 What? Yeah, one of them is Darian.
02:19:55.736 --> 02:19:58.890 Yeah, but, but aren't there two that are Darian? At least it
02:19:55.796 --> 02:19:56.116 Yeah.
02:19:58.890 --> 02:19:59.976 seems like there are.
02:19:59.826 --> 02:20:00.496 There was.
02:20:01.106 --> 02:20:03.376 So then the rest of them all say NA.
02:20:01.886 --> 02:20:02.316 Yeah.
02:20:04.366 --> 02:20:09.034 Which means that our indexing logic is probably not storing
02:20:09.034 --> 02:20:11.836 this the city onto those correctly.
02:20:13.406 --> 02:20:15.913 So that's fine. We'll we'll figure out why, because
02:20:15.913 --> 02:20:18.276 obviously the front end is showing it correctly.
02:20:19.616 --> 02:20:22.332 So we need to look at how the front end is displaying what
02:20:22.332 --> 02:20:24.726 city that job is in, and then figure out if we can.
02:20:25.276 --> 02:20:28.226 You're breaking up. I don't know if it's me or.
02:20:28.626 --> 02:20:31.342 It might be me, my headsets beeping that it's dying. Give me
02:20:31.342 --> 02:20:31.966 just a second.
02:20:33.606 --> 02:20:34.066 Yeah.
02:20:39.316 --> 02:20:40.576 Is the Internet working?
02:20:43.536 --> 02:20:44.146 I hear you.
02:20:45.456 --> 02:20:46.386 You hear me or.
02:20:45.566 --> 02:20:46.356 I'm still here.
02:20:47.516 --> 02:20:48.466 I hear both of you.
02:20:47.886 --> 02:20:50.156 Ohh. Ohm yeah, you're still here.
02:20:50.776 --> 02:20:51.146 Yeah.
02:20:51.536 --> 02:20:55.633 Well, that is fantastic. You get, uh, you get to enjoy the
02:20:55.633 --> 02:20:58.966 the wonderful world of Elasticsearch debugging.
02:20:56.396 --> 02:20:56.946 Yeah.
02:21:00.116 --> 02:21:00.926 Yeah, that's.
02:21:02.466 --> 02:21:03.436 Let's see this.
02:21:04.276 --> 02:21:04.756 So.
02:21:06.486 --> 02:21:07.076 OK.
02:21:08.176 --> 02:21:11.011 So that's all fine. Obviously, like I said, we see that it's
02:21:11.011 --> 02:21:13.939 putting the like the front end nose where the data is supposed
02:21:13.939 --> 02:21:16.635 to come from, cause it's rendering it correctly. So we're
02:21:16.635 --> 02:21:19.378 probably just pulling it from the wrong place and the dump
02:21:19.378 --> 02:21:22.259 reader, which is perfectly fine. That's easily fixable. We'll
02:21:22.259 --> 02:21:25.141 just go look at the front end code here in a minute, but that
02:21:25.141 --> 02:21:26.536 at least confirms for us 100%.
02:21:27.226 --> 02:21:30.155 We have a problem in our date and the the dump reader the like
02:21:30.155 --> 02:21:33.038 the indexing part of our code, so that's cool. We've isolated
02:21:33.038 --> 02:21:33.736 the city issue.
02:21:34.296 --> 02:21:36.586 Uh, alright, so let's step over.
02:21:39.236 --> 02:21:41.466 We're basically just going to walk this thing all the way out.
02:21:41.926 --> 02:21:45.066 Uh backup tour returns the result because.
02:21:43.016 --> 02:21:43.276 OK.
02:21:46.136 --> 02:21:47.446 Clearly, like we've seen.
02:21:48.206 --> 02:21:49.606 Something is is.
02:21:50.476 --> 02:21:52.967 Messing up the result and returning that. There's only
02:21:52.967 --> 02:21:53.556 eight things.
02:21:54.536 --> 02:21:55.326 UM.
02:21:57.396 --> 02:22:01.903 Alright, so let's go look at UM result dot total down there on
02:22:01.903 --> 02:22:02.476 line 70.
02:22:03.496 --> 02:22:04.796 Should still be 23.
02:22:06.216 --> 02:22:11.706 It is OK total pages OK, that's fine it it calculates that so.
02:22:13.776 --> 02:22:15.766 Alright, so keep keep stepping over.
02:22:17.196 --> 02:22:18.366 OK, keep going.
02:22:20.106 --> 02:22:22.136 We can pretty much step over all of this, I think.
02:22:29.756 --> 02:22:32.456 Yeah. So, uh, just keep stepping until we're out of this method.
02:22:35.736 --> 02:22:36.666 Yep, you're gone.
02:22:38.106 --> 02:22:39.996 You going alright?
02:22:41.136 --> 02:22:44.196 Now, where do we land after this? Go ahead and step over.
02:22:45.836 --> 02:22:48.826 OK, we're at whatever called this, which is.
02:22:53.436 --> 02:22:56.566 The searching thing. OK, that's fine. Just step over. This is
02:22:56.566 --> 02:22:59.596 one of those like 700 line methods in here that's not worth
02:22:59.596 --> 02:23:00.606 reading through, OK.
02:23:01.446 --> 02:23:03.834 Now we're looking at something that looks like it's gonna do
02:23:03.834 --> 02:23:04.226 some crap.
02:23:05.106 --> 02:23:08.676 Uh, OK, so step over once.
02:23:10.156 --> 02:23:15.171 And mouse over ID's that should be an array of nine things. Yes.
02:23:15.171 --> 02:23:15.866 OK, good.
02:23:17.186 --> 02:23:21.370 OK, keep rolling. We should end up just stepping over pretty
02:23:21.370 --> 02:23:22.536 much all of this.
02:23:28.606 --> 02:23:31.256 Scroll down a little bit. Let's make sure we don't.
02:23:32.076 --> 02:23:33.256 Step or anything important.
02:23:34.076 --> 02:23:34.876 Yeah, OK, just keep.
02:23:34.226 --> 02:23:34.436 Yeah.
02:23:35.766 --> 02:23:38.196 We'll go past all this like data cleanup stuff.
02:23:42.276 --> 02:23:42.946 OK.
02:23:44.446 --> 02:23:45.396 Yeah, keep going.
02:23:49.026 --> 02:23:49.756 All right.
02:23:52.156 --> 02:23:53.046 Back out.
02:23:54.246 --> 02:23:57.307 OK, step over and this is not going to throw because we've
02:23:57.307 --> 02:23:58.656 already seen it not throw.
02:23:59.446 --> 02:24:00.596 Came mouse over view model.
02:24:03.726 --> 02:24:04.556 Expand.
02:24:06.376 --> 02:24:08.306 Account 9 results ID.
02:24:06.686 --> 02:24:11.426 OK, so So what now? And now it's just gonna work, I guess.
02:24:12.926 --> 02:24:16.822 We didn't change anything and it's just it's just gonna decide
02:24:16.822 --> 02:24:17.936 that it works now.
02:24:21.566 --> 02:24:23.396 Classic. OK.
02:24:25.766 --> 02:24:26.816 Alright, just continue.
02:24:30.516 --> 02:24:31.976 The only thing we changed.
02:24:32.876 --> 02:24:34.566 Was we changed the.
02:24:36.146 --> 02:24:39.868 We changed Cabana, but Kibana shouldn't interface shouldn't
02:24:39.868 --> 02:24:42.536 intercept any queries to elastic directly.
02:24:43.176 --> 02:24:45.456 And we're still seeing a one of eight down there.
02:24:47.206 --> 02:24:50.096 So find the the call to the actual query, yeah.
02:24:51.126 --> 02:24:53.676 And we still got it saying total of 8.
02:24:54.846 --> 02:24:55.976 OK, scroll up some more.
02:24:58.476 --> 02:25:01.690 Were there other query calls? Yeah. OK, so there's at least
02:25:01.690 --> 02:25:02.976 two. That one's correct.
02:25:07.596 --> 02:25:09.594 All right, so what's the difference between those two
02:25:09.594 --> 02:25:09.816 calls?
02:25:13.946 --> 02:25:17.436 And why is it so? I would say the bug now looks to be.
02:25:18.616 --> 02:25:19.826 A twofold issue.
02:25:20.556 --> 02:25:23.386 One of them's. Ohh, the second one's job resumes.
02:25:25.716 --> 02:25:27.306 So it ran both.
02:25:31.656 --> 02:25:32.956 And presumably.
02:25:35.516 --> 02:25:39.831 So it looks like it's displaying a resume. Is this a resume, a
02:25:35.536 --> 02:25:36.326 OK so.
02:25:39.831 --> 02:25:41.886 associated with a job posting?
02:25:42.936 --> 02:25:44.616 I think it's just a resume.
02:25:45.426 --> 02:25:48.134 Because I bet you clarity account is set up as an
02:25:48.134 --> 02:25:49.976 employer, not a not a job seeker.
02:25:51.006 --> 02:25:53.656 Oh, it is, yeah.
02:25:56.006 --> 02:25:57.956 Yeah, that's for sure it is, yeah.
02:25:58.996 --> 02:26:01.306 OK, we definitely need.
02:26:00.276 --> 02:26:02.516 So these are resumes where surgery.
02:26:03.376 --> 02:26:07.292 Apparently so there's there's not really any indication of
02:26:07.292 --> 02:26:10.346 that anywhere, so we'd probably want that to.
02:26:12.676 --> 02:26:14.286 Probably want that to be more clear.
02:26:12.826 --> 02:26:14.146 But it's using the job.
02:26:14.886 --> 02:26:18.726 It's using the job search Tesco local.
02:26:19.656 --> 02:26:21.096 Search it. That's not the.
02:26:20.016 --> 02:26:22.586 It's running well. It's it's running both.
02:26:23.136 --> 02:26:24.196 Ohh OK.
02:26:24.716 --> 02:26:27.520 Yeah, that's what I noticed. If you pulled that back out a lot
02:26:27.520 --> 02:26:28.366 wider, you can see.
02:26:29.846 --> 02:26:32.820 The first one is sending the request to slash searching slash
02:26:32.820 --> 02:26:35.602 job openings and the 2nd is sending it to slash searching
02:26:35.602 --> 02:26:36.466 slash job resumes.
02:26:37.596 --> 02:26:41.903 OK, so this is the resumes one that is returning 8 and that's
02:26:41.903 --> 02:26:44.266 what we're seeing in the catalog.
02:26:43.356 --> 02:26:46.862 And that's what we're seeing in the catalog. So you're seeing
02:26:46.862 --> 02:26:50.424 the resume catalog, not the job opening catalog. So we need to
02:26:50.424 --> 02:26:54.043 switch it. Excuse me, we need to switch this. Yeah, log out and
02:26:54.043 --> 02:26:55.966 log in as someone that is seeker.
02:26:54.436 --> 02:26:57.942 It's where it's where I logged into the admin in the same
02:26:57.942 --> 02:26:58.366 window.
02:27:13.456 --> 02:27:14.506 No, I have 23.
02:27:16.716 --> 02:27:17.606 For even loads.
02:27:17.016 --> 02:27:18.736 OK. Well, that's good.
02:27:19.816 --> 02:27:21.056 That's good, but we.
02:27:24.056 --> 02:27:25.026 Well, we definitely.
02:27:24.186 --> 02:27:25.456 We rabbit holed.
02:27:25.906 --> 02:27:29.896 Little bit, but hey, we got your cabana working that positive.
02:27:26.236 --> 02:27:26.596 We're.
02:27:33.936 --> 02:27:35.306 So if I do.
02:27:37.746 --> 02:27:40.576 We're still only going to see the one in here, I think. And
02:27:40.576 --> 02:27:43.265 again I think that's just because we've got some kind of
02:27:43.265 --> 02:27:44.256 data issue somewhere.
02:27:45.086 --> 02:27:48.186 I've been curious this whole time. What's that TM graph thing
02:27:48.186 --> 02:27:49.736 on the right side? What's that?
02:27:50.326 --> 02:27:54.386 It's a it's a carousel showing ads. They just all happen to be
02:27:54.386 --> 02:27:56.256 pointing to the same picture.
02:27:56.976 --> 02:27:58.976 OK. That's like.
02:27:58.316 --> 02:27:58.776 Yeah.
02:27:58.336 --> 02:28:01.383 Uh, you had a you had a break point on the back and that's why
02:28:01.383 --> 02:28:01.916 it's stuck.
02:28:03.336 --> 02:28:04.566 You can remove that break point.
02:28:06.486 --> 02:28:07.426 And I just continue.
02:28:13.916 --> 02:28:18.206 It's thinking alright, OK, they are. We still only have the one.
02:28:18.966 --> 02:28:22.565 But that's fixable if we go look at where that's coming from on
02:28:22.565 --> 02:28:23.296 the back end.
02:28:25.796 --> 02:28:27.406 Or I'm sorry on the front end so.
02:28:26.246 --> 02:28:27.066 Umm so we.
02:28:31.186 --> 02:28:34.678 We need to find the job opening card, whatever. Whatever is
02:28:34.678 --> 02:28:37.006 displaying that they're in the catalog.
02:28:37.946 --> 02:28:38.706 Umm.
02:28:42.636 --> 02:28:45.792 They don't know where that would be. It would be able to
02:28:45.792 --> 02:28:46.346 dashboard.
02:28:51.316 --> 02:28:52.506 To it's not that.
02:28:53.826 --> 02:28:57.180 Uh try list view because I think that's what we're looking at is
02:28:57.180 --> 02:28:57.696 list view.
02:28:58.986 --> 02:29:02.352 Catalog, list, view and task the task you'll override. Yeah, that
02:28:59.896 --> 02:29:00.326 I love.
02:29:02.352 --> 02:29:02.556 one.
02:29:04.236 --> 02:29:05.386 Probably in here.
02:29:24.116 --> 02:29:28.934 OK, so it says job location is location info dot job city dot
02:29:28.934 --> 02:29:33.130 value. So where's it getting that from? Click on that
02:29:33.130 --> 02:29:37.016 location info serializable attributes dictionary?
02:29:42.226 --> 02:29:42.996 Concerning.
02:29:44.646 --> 02:29:49.266 OK, So what calls get location then on line 58?
02:29:51.336 --> 02:29:54.748 Because that's going to be what's passing in job dot
02:29:54.748 --> 02:29:58.546 serializable attributes. So apparently the city state and.
02:29:59.676 --> 02:30:02.558 Whatever the other thing was might have been postal code or
02:30:02.558 --> 02:30:05.297 actually being stored in serializable attributes instead
02:30:05.297 --> 02:30:06.066 of on a contact.
02:30:07.216 --> 02:30:08.806 Which is a problem.
02:30:07.836 --> 02:30:13.076 All kinds of **** this stored in serialized wash everything.
02:30:12.636 --> 02:30:15.086 Yeah. Yeah, that's.
02:30:16.536 --> 02:30:18.236 OK, unfortunate.
02:30:21.136 --> 02:30:23.346 That explains why we weren't seeing it in a data.
02:30:28.206 --> 02:30:29.396 So yeah, I see zip.
02:30:30.346 --> 02:30:34.375 Ohh company contact name St Region all of it is in job
02:30:34.375 --> 02:30:38.697 attributes with the word job appended to what it would be.
02:30:38.697 --> 02:30:42.653 The field would be in Seth right? So job company, job
02:30:42.653 --> 02:30:43.606 contact name.
02:30:45.836 --> 02:30:51.181 Job region, job city all that's in serializable attributes on
02:30:51.181 --> 02:30:51.526 the.
02:30:56.916 --> 02:30:57.986 Job object.
02:31:04.986 --> 02:31:05.676 OK.
02:31:07.126 --> 02:31:07.596 Well.
02:31:10.986 --> 02:31:11.776 That's.
02:31:14.206 --> 02:31:15.966 That's going to make things complicated.
02:31:17.286 --> 02:31:20.033 This thing should have been most of that looks like it should
02:31:20.033 --> 02:31:22.736 have been stored in the contact that's tied to their record.
02:31:24.206 --> 02:31:27.036 Yeah, it literally has a contact on the record.
02:31:27.556 --> 02:31:31.989 Yeah. So all that stuff should have been assigned in that, but
02:31:31.989 --> 02:31:35.226 we don't really have the time to go back and.
02:31:36.186 --> 02:31:37.096 Change it all.
02:31:38.436 --> 02:31:38.846 No.
02:31:39.686 --> 02:31:42.872 So we're just gonna have to work with what we've got or play the
02:31:42.872 --> 02:31:44.196 play. The hand we're dealt.
02:31:45.496 --> 02:31:45.956 So.
02:31:51.226 --> 02:31:55.182 Does that mean we need to modify electric search to look for
02:31:55.182 --> 02:31:59.203 these values in the serializable attributes instead of on the
02:31:59.203 --> 02:32:00.176 actual contact?
02:32:00.526 --> 02:32:04.043 Close. Instead, we're going to modify the dump reader to read
02:32:04.043 --> 02:32:07.334 them out of the attributes and index them the same way we
02:32:07.334 --> 02:32:10.511 already have been. That way, Elastic doesn't have to do
02:32:10.511 --> 02:32:14.199 anything differently, we just we just feed it the data different
02:32:14.199 --> 02:32:14.426 way.
02:32:15.396 --> 02:32:16.106 OK.
02:32:15.506 --> 02:32:19.065 So what we're going to need to do, we're already reading the
02:32:19.065 --> 02:32:22.741 JSON attributes out on line 52, so that's good. All that we'll
02:32:22.741 --> 02:32:26.534 need to do is that contact City, we're gonna do something that's
02:32:26.534 --> 02:32:27.876 kind of similar to the.
02:32:27.956 --> 02:32:28.426 Umm.
02:32:29.856 --> 02:32:33.939 Uh, the latitude, longitude thing we did earlier, we're
02:32:33.939 --> 02:32:37.586 gonna add a go and Scroll down just a little bit.
02:32:36.706 --> 02:32:37.166 Ohh.
02:32:39.246 --> 02:32:43.276 A little bit more. It's after this indexable model thing. OK,
02:32:43.276 --> 02:32:45.226 we're gonna add a city to use.
02:32:50.376 --> 02:32:53.143 Yeah. And then it's going to be equals version dot city or
02:32:53.143 --> 02:32:54.316 contact city or whatever.
02:32:55.016 --> 02:32:55.326 Yeah.
02:32:57.036 --> 02:32:59.006 And then we're going to do if.
02:33:00.596 --> 02:33:03.606 If not contract dot check valid key.
02:33:12.716 --> 02:33:13.646 And then city.
02:33:16.736 --> 02:33:20.668 Yep. And then in the body of that, then we're going to
02:33:20.668 --> 02:33:24.671 deserialize the attribute dictionary off of the version
02:33:24.671 --> 02:33:28.818 and then try to read the the city attribute off of it and
02:33:28.818 --> 02:33:33.108 store it into that. And then I'll be right back. I gotta go
02:33:33.108 --> 02:33:33.966 get a drink.
02:33:49.516 --> 02:33:51.866 Serialize that it's.
02:34:02.876 --> 02:34:03.286 Version.
02:34:15.516 --> 02:34:17.116 Jake's gonna attributes OK?
02:34:24.666 --> 02:34:26.666 Jason attributes.
02:34:30.146 --> 02:34:30.956 Job.
02:34:33.496 --> 02:34:35.016 That right, Tristan?
02:34:37.066 --> 02:34:39.819 What are we doing? Have I'll work with backward too, so we
02:34:39.819 --> 02:34:40.006 got.
02:34:40.246 --> 02:34:43.626 I'm trying to read a value out of the serialized attributes of
02:34:43.626 --> 02:34:45.666 the Jason attributes in the back end.
02:34:48.006 --> 02:34:51.913 So if you hover over Jason attributes, first of all do you
02:34:51.913 --> 02:34:54.496 have JSON attributes already or cause?
02:34:53.746 --> 02:34:54.536 Yeah, yeah.
02:34:56.506 --> 02:34:57.486 It's on this version.
02:35:00.396 --> 02:35:03.365 OK, so version is like the actual like thing you queried
02:35:00.696 --> 02:35:01.136 It's a.
02:35:03.365 --> 02:35:06.126 right from the database or whatever. What's that OK.
02:35:04.226 --> 02:35:07.044 Yeah, yeah, yeah. It's a job opening. It's just an honest
02:35:07.044 --> 02:35:09.036 one. Cause we did this select statement.
02:35:09.556 --> 02:35:11.286 So if you.
02:35:10.406 --> 02:35:11.186 Walking back.
02:35:10.616 --> 02:35:12.266 So it's a job opening model.
02:35:13.286 --> 02:35:16.941 It's not a model, it's a. It's stuff out of the database, but
02:35:13.566 --> 02:35:15.316 I always mix these up in my head.
02:35:16.616 --> 02:35:18.758 Do you get stuff from Jason attributes you get from
02:35:16.941 --> 02:35:17.236 yeah.
02:35:18.758 --> 02:35:20.736 Serializable attributes dictionary when you're?
02:35:20.016 --> 02:35:23.529 Serializable attributes dictionary the JSON attributes
02:35:22.976 --> 02:35:23.346 OK.
02:35:23.529 --> 02:35:27.299 is just a string, which is why it's complaining. So you're
02:35:25.526 --> 02:35:25.786 Yeah.
02:35:25.666 --> 02:35:26.336 OK.
02:35:27.299 --> 02:35:30.940 going to do is do VAR attributes equals version dot JSON
02:35:30.940 --> 02:35:34.710 attributes dot B serialize something, something something.
02:35:33.576 --> 02:35:34.376 OK.
02:35:34.710 --> 02:35:38.671 Yeah, so the JSON attributes column in the database is just a
02:35:36.066 --> 02:35:36.536 Uh.
02:35:38.671 --> 02:35:42.568 string column. There you go. Yeah. Now this converts it into
02:35:42.568 --> 02:35:46.146 an actual object that we can query against and whatnot.
02:35:47.166 --> 02:35:49.526 Umm. And then the proper way to do this would be.
02:35:50.276 --> 02:35:50.726 Uh.
02:35:51.546 --> 02:35:54.491 Just to make sure that we're robust against uh errors and
02:35:54.491 --> 02:35:55.456 what not, do it if.
02:35:57.746 --> 02:36:00.496 And then attributes dot try get value.
02:36:02.526 --> 02:36:03.766 I get value that's.
02:36:04.386 --> 02:36:08.654 Yeah. And then you put in the key, which is gonna be whatever
02:36:05.396 --> 02:36:06.386 That's gonna be.
02:36:08.654 --> 02:36:12.990 job city I think. Yeah. And then out VAR value or out Var city
02:36:12.990 --> 02:36:15.056 attribute in the in the thing.
02:36:15.996 --> 02:36:17.806 Uh. Parentheses before that? Yeah.
02:36:18.306 --> 02:36:18.876 Ohh.
02:36:19.206 --> 02:36:19.436 Yep.
02:36:20.256 --> 02:36:21.006 My dear.
02:36:21.896 --> 02:36:22.456 Ship.
02:36:23.056 --> 02:36:24.136 I do that all the time.
02:36:23.816 --> 02:36:27.646 Out of our out of our city.
02:36:26.646 --> 02:36:30.396 This uh, like city city attribute or city a TR.
02:36:31.336 --> 02:36:34.126 So it doesn't have to be super long variable name.
02:36:35.656 --> 02:36:37.566 Uh, OK. And then in the body?
02:36:41.746 --> 02:36:46.656 Do city equals city Atsr question Mark dot value?
02:36:53.036 --> 02:36:53.326 OK.
02:36:53.956 --> 02:36:59.046 Cool. So that'll make it so that if we didn't read a city off of
02:36:59.046 --> 02:37:03.666 the contact attached to the record, then we'll try to fall
02:37:03.666 --> 02:37:06.956 back to reading it out of the attributes.
02:37:07.856 --> 02:37:10.795 Should we do that with the other ones that are stored there like
02:37:10.795 --> 02:37:10.976 job?
02:37:11.666 --> 02:37:13.286 Name or like job.
02:37:14.046 --> 02:37:15.296 Company would be.
02:37:16.946 --> 02:37:18.626 Company name, right?
02:37:18.326 --> 02:37:21.626 That would probably be smart.
02:37:22.886 --> 02:37:25.256 Gotta love the serializable attributes abuse.
02:37:22.986 --> 02:37:23.786 I would think so.
02:37:26.156 --> 02:37:26.416 Yeah.
02:37:31.506 --> 02:37:34.326 The main and then we would do.
02:37:35.366 --> 02:37:37.506 Getting pretty much copy that whole thing right there.
02:37:37.766 --> 02:37:38.286 Yeah.
02:37:38.396 --> 02:37:41.054 That you have and then just replace every instance of city
02:37:41.054 --> 02:37:41.866 with company name.
02:37:44.536 --> 02:37:46.106 Ship like it's see again.
02:37:47.856 --> 02:37:49.426 Have also done that before.
02:37:51.456 --> 02:37:53.136 And so it's job.
02:37:54.116 --> 02:37:54.476 Come.
02:37:55.466 --> 02:37:57.556 The name of your job company.
02:37:59.256 --> 02:37:59.656 Now.
02:38:01.816 --> 02:38:05.076 Yeah, just high do the do the cool trick I showed earlier.
02:38:04.756 --> 02:38:06.676 Umm yeah.
02:38:06.716 --> 02:38:11.455 So control Z that back to city and then select the word city
02:38:11.455 --> 02:38:13.786 Online 112 and then shift alt.
02:38:15.626 --> 02:38:19.276 Oh wait, I want twelve. Yeah, so shift off.
02:38:17.746 --> 02:38:21.083 Yeah. And then just yeah, shift also selects all the ones
02:38:21.083 --> 02:38:23.616 underneath that shift alt period. I got it.
02:38:24.496 --> 02:38:25.466 And then company name.
02:38:35.886 --> 02:38:39.847 Yay, OK. And then the last thing you'll do after both of those
02:38:36.396 --> 02:38:37.016 Yeah.
02:38:39.847 --> 02:38:40.036 is.
02:38:40.646 --> 02:38:45.576 UM indexable model dot city equals whatever.
02:38:47.276 --> 02:38:51.443 Yeah, I'm. I'm gonna make sure. Let's see. We need we're
02:38:51.443 --> 02:38:55.684 filtering on or we're searching on company name. City SEO
02:38:55.684 --> 02:38:57.366 keywords, which is not.
02:39:00.266 --> 02:39:01.746 Not stored in the attributes.
02:39:03.016 --> 02:39:04.446 I don't think so. I'm gonna make sure.
02:39:05.256 --> 02:39:06.686 I'm going to lose my mind if it is.
02:39:07.586 --> 02:39:13.968 No, no keywords and then so location and he. So we need
02:39:13.968 --> 02:39:15.906 street from here.
02:39:16.896 --> 02:39:19.226 Or no, we need we need postal code, right?
02:39:22.146 --> 02:39:24.166 Potentially, unfortunately.
02:39:22.166 --> 02:39:24.576 City, region, state.
02:39:26.086 --> 02:39:27.676 Zip job zip.
02:39:28.066 --> 02:39:30.386 OK, so if that's in there, then yeah, we probably need to read
02:39:30.386 --> 02:39:32.376 that out and use that for the distance filtering too.
02:39:40.086 --> 02:39:43.166 So it's contact City? Nope.
02:39:43.326 --> 02:39:45.416 From there, So what you'll probably have to do.
02:39:46.756 --> 02:39:47.286 Is.
02:39:51.626 --> 02:39:53.016 We're gonna make some adjustments.
02:39:52.216 --> 02:39:52.926 We've launched.
02:39:55.736 --> 02:39:59.076 We could query it out. You just copy like the contact address
02:39:59.076 --> 02:40:02.200 city, that last line and then add contact postal code and
02:40:02.200 --> 02:40:05.432 Change city to postal code. Just copy that whole line right
02:40:05.432 --> 02:40:05.756 there.
02:40:07.366 --> 02:40:08.056 The whole line.
02:40:08.506 --> 02:40:11.904 Yeah, just copy paste that whole line like into here so we can
02:40:11.904 --> 02:40:15.302 query it out the entire line and then change anything in there
02:40:15.302 --> 02:40:17.136 city on that line to postal code.
02:40:20.726 --> 02:40:21.256 OK.
02:40:21.466 --> 02:40:23.346 They paste it in that in that query up there.
02:40:24.596 --> 02:40:29.286 Ohh yeah duh, because we don't have the postal code. Yeah, OK.
02:40:25.196 --> 02:40:26.616 Like actually going to query it out.
02:40:28.286 --> 02:40:28.976 Yeah, yeah.
02:40:29.286 --> 02:40:29.956 And then.
02:40:29.326 --> 02:40:30.106 Uh.
02:40:30.856 --> 02:40:31.406 Umm.
02:40:34.006 --> 02:40:34.536 OK.
02:40:35.406 --> 02:40:37.196 And it should be called postal code here.
02:40:39.726 --> 02:40:41.056 Style.
02:40:42.066 --> 02:40:44.436 Yeah, sweet. OK. So now we'll have that.
02:40:45.056 --> 02:40:47.166 And UM.
02:40:49.526 --> 02:40:52.786 Yeah, version dot put the contact post code. Yep, and then
02:40:52.786 --> 02:40:56.047 we'll do the same thing. One more time of if it's, if it's
02:40:56.047 --> 02:40:57.816 not in there, then we'll set it.
02:41:10.186 --> 02:41:11.176 Thank you. Called it zip.
02:41:12.756 --> 02:41:13.146 I did.
02:41:14.596 --> 02:41:15.526 Nice and short.
02:41:17.576 --> 02:41:22.176 And then job company Online 125, we'll change to job sip.
02:41:24.276 --> 02:41:25.256 That miss? Ohh yeah.
02:41:31.886 --> 02:41:35.548 Cool. And then, OK, so then before we do anything else,
02:41:32.066 --> 02:41:32.576 OK.
02:41:35.548 --> 02:41:39.603 let's make sure that we set the city and company name back on
02:41:39.603 --> 02:41:43.593 the indexable model. So we don't forget to do that. So after
02:41:43.593 --> 02:41:44.836 everything is done.
02:41:45.396 --> 02:41:47.906 Umm, it's still gonna be in the dump reader.
02:41:49.916 --> 02:41:53.485 We created indexable model right there. We need to actually
02:41:53.485 --> 02:41:56.816 backfill all of this data onto like anything that we've
02:41:56.816 --> 02:42:00.563 changed. So City company name, et cetera. All that needs to be
02:42:00.563 --> 02:42:02.586 stored on to the INDEXABLE model.
02:42:03.466 --> 02:42:06.756 So after we've done all the post processing of it further down.
02:42:04.156 --> 02:42:04.596 Ohh.
02:42:11.286 --> 02:42:13.745 Yes, somewhere down here, just assign those values onto the
02:42:13.745 --> 02:42:15.836 indexable model. Yeah, like down there at the end.
02:42:17.446 --> 02:42:18.056 Like right here.
02:42:20.206 --> 02:42:22.838 I yeah, I would put it a little closer to where we're actually
02:42:22.736 --> 02:42:23.466 We're right here.
02:42:22.838 --> 02:42:24.886 doing the value changes. Yeah, like right there.
02:42:25.996 --> 02:42:28.216 It's OK, so Indexable, bought.
02:42:30.566 --> 02:42:32.306 Indexible models dot.
02:42:33.386 --> 02:42:38.076 Contact City gets job. Sit what I call it.
02:42:38.446 --> 02:42:39.596 I think you just called it city.
02:42:40.516 --> 02:42:42.456 City company name and ZIP, OK.
02:42:43.906 --> 02:42:46.955 And the zip one, we're actually not going to be feeding into it
02:42:46.955 --> 02:42:50.052 because it doesn't have a thing for that. But we're gonna modify
02:42:50.052 --> 02:42:52.816 the logic for that, ensure lat long on address to accept.
02:42:53.776 --> 02:42:57.076 The postal code value from there.
02:42:58.596 --> 02:42:58.956 OK.
02:42:58.676 --> 02:43:01.936 Cool, so save.
02:43:03.816 --> 02:43:07.147 All of that and then click on that ensure lat long on address
02:43:07.147 --> 02:43:09.726 and pretty much what we're going to do here is.
02:43:11.986 --> 02:43:13.666 We're gonna pass in.
02:43:14.376 --> 02:43:16.546 A nullable string.
02:43:17.746 --> 02:43:22.266 It's called zip attribute I guess.
02:43:25.726 --> 02:43:26.216 Yeah, that works.
02:43:27.186 --> 02:43:29.326 And then what we wanna do down here.
02:43:30.306 --> 02:43:31.336 Is.
02:43:36.856 --> 02:43:40.666 Let's see if the address is not null.
02:43:41.526 --> 02:43:43.576 Then we try to read the coordinates.
02:43:45.126 --> 02:43:50.460 Out of the yeah. So we're going to slightly adjust this. So now
02:43:50.460 --> 02:43:55.712 what we're going to do is remove the else on line 205, so that
02:43:55.712 --> 02:43:57.046 it's just an if.
02:44:01.406 --> 02:44:06.572 OK. And then go back into or go up one line right above that.
02:44:06.572 --> 02:44:11.156 And then between those we're gonna do var postal code.
02:44:15.766 --> 02:44:20.556 Equals address question Mark dot postalcode.
02:44:23.806 --> 02:44:27.156 And then double question Mark Zip a TR.
02:44:30.166 --> 02:44:34.545 Yeah. Perfect. OK. And then instead of doing if address is
02:44:34.545 --> 02:44:39.073 not equal to null do if postal code if if contract dot check
02:44:39.073 --> 02:44:40.706 valid key postal code.
02:44:55.476 --> 02:44:58.170 And then online, 2:10 that now has the error. We're gonna
02:44:58.170 --> 02:45:00.726 replace that with just our local postal code variable.
02:45:02.176 --> 02:45:02.636 OK.
02:45:03.306 --> 02:45:07.305 And then a little bit further down, we're going to change this
02:45:07.305 --> 02:45:07.686 to be.
02:45:10.226 --> 02:45:14.450 OK, so inside of there wrap the address section in a check for
02:45:14.450 --> 02:45:16.596 if address is not equal to null.
02:45:17.896 --> 02:45:18.926 Inside of.
02:45:19.236 --> 02:45:22.778 The chords is not equal to null. So yeah, right there, hit enter
02:45:22.778 --> 02:45:25.286 and then do. If address is not equal to null.
02:45:32.906 --> 02:45:35.538 Yeah. And then moved those. Those next three lines all go
02:45:33.106 --> 02:45:33.936 And we're gonna put.
02:45:35.538 --> 02:45:37.536 inside of that, including the context save.
02:45:38.596 --> 02:45:39.036 OK.
02:45:41.996 --> 02:45:44.226 Yep, and that should be it.
02:45:45.746 --> 02:45:47.656 Or should that extra blank line and?
02:45:48.306 --> 02:45:51.572 And then it's going to obviously we have an error because we
02:45:51.572 --> 02:45:54.571 added a parameter to this method. So we just need to go
02:45:54.571 --> 02:45:57.356 past the ZIP code into this method from the thingy.
02:46:01.416 --> 02:46:04.346 Yeah, right there. And then it'll be you can zip comma.
02:46:05.306 --> 02:46:08.376 And then this should be a little bit more.
02:46:10.816 --> 02:46:11.476 Functional.
02:46:14.566 --> 02:46:15.156 So.
02:46:17.376 --> 02:46:18.446 Touch.
02:46:19.946 --> 02:46:21.496 Pictures save all.
02:46:21.996 --> 02:46:25.324 Do you guys ever see pictures that joke about the way
02:46:23.026 --> 02:46:23.276 Good.
02:46:25.324 --> 02:46:28.836 landlords at like cheap apartments repair stuff? Is they
02:46:28.836 --> 02:46:32.719 just like, put a massive like quarter inch thick coat of paint
02:46:32.719 --> 02:46:35.246 on it. They called the landlord special.
02:46:36.856 --> 02:46:38.386 Yeah, yeah, yeah.
02:46:37.216 --> 02:46:39.466 I'm not not shocked.
02:46:40.516 --> 02:46:42.456 Well, that's what. That's what it feels like when.
02:46:43.316 --> 02:46:45.366 When, like you're going, you're kind of like.
02:46:46.376 --> 02:46:49.623 Like the ideal way to fix something like this would be
02:46:49.623 --> 02:46:53.343 storing it on the right records and cleaning it all up, but we
02:46:53.343 --> 02:46:57.181 can't. We don't really have the time and and we don't wanna burn
02:46:57.181 --> 02:47:00.783 client money on on that when we can't. We do have a solution
02:47:00.783 --> 02:47:02.496 that takes less time for now.
02:47:03.466 --> 02:47:06.245 So when we're doing things like this is just like, Oh yeah, read
02:47:06.245 --> 02:47:08.897 it off like attributes and do all this, like, fall back stuff
02:47:08.897 --> 02:47:11.506 and change it a little change this change that but you know.
02:47:12.236 --> 02:47:15.266 Doesn't take as long, but it's still a little bit messy. That's
02:47:15.266 --> 02:47:16.356 the landlord's special.
02:47:17.876 --> 02:47:18.246 It.
02:47:19.606 --> 02:47:20.406 Yeah, don't worry about it.
02:47:21.446 --> 02:47:23.874 Because now if we need to attach in here, it's gonna complain
02:47:23.874 --> 02:47:26.223 that it doesn't match. I guess the single builds don't take
02:47:25.786 --> 02:47:28.666 Uh, yeah, no, it takes just a second.
02:47:26.223 --> 02:47:27.046 long, so that's fine.
02:47:30.026 --> 02:47:31.116 Yeah. OK.
02:47:30.206 --> 02:47:34.228 Alright, cool. Let's see. Let's see where we're at. We're gonna
02:47:34.228 --> 02:47:37.056 need to reindex. Clear the Redis caches and.
02:47:38.236 --> 02:47:40.826 We'll see where where our uh search is at now.
02:47:42.256 --> 02:47:44.086 I'm feeling pretty good about it.
02:47:42.426 --> 02:47:43.436 So let me.
02:47:46.956 --> 02:47:48.636 Me go, this is the.
02:48:03.636 --> 02:48:06.846 You're hot, man. Thank you for helping me, dude. Cause.
02:48:06.276 --> 02:48:06.756 No problem.
02:48:08.406 --> 02:48:11.877 It would have took me longer than 2 1/2 hours to to debug
02:48:11.877 --> 02:48:12.656 this I think.
02:48:15.186 --> 02:48:17.576 And we got a got your cabana working.
02:48:18.746 --> 02:48:22.775 And you learned a lot about the last six search and how
02:48:19.276 --> 02:48:19.806 Yeah.
02:48:20.856 --> 02:48:21.436 Yeah.
02:48:22.775 --> 02:48:26.086 physically painful it can be to troubleshoot.
02:48:27.536 --> 02:48:28.056 Yeah.
02:48:33.866 --> 02:48:37.516 I bet some of those records don't even have a.
02:48:39.006 --> 02:48:41.136 The contact information on the contact.
02:48:41.866 --> 02:48:42.886 And some of them do.
02:48:42.216 --> 02:48:44.597 Yeah, they they definitely don't. That's why we weren't
02:48:44.597 --> 02:48:47.148 getting. We were only getting it on some of them and not on
02:48:47.148 --> 02:48:47.446 others.
02:48:49.306 --> 02:48:51.056 Well, that's not accurate.
02:48:53.296 --> 02:48:56.180 If you want to do this where it's not gonna log you out of
02:48:56.180 --> 02:48:59.406 the test one so we don't have to keep switching open an Incognito
02:48:59.406 --> 02:49:02.388 tab and then do, uh, log into clarity in Incognito. That way
02:48:59.906 --> 02:49:00.426 Yeah.
02:49:02.388 --> 02:49:03.806 you'll have the admin window.
02:49:02.456 --> 02:49:04.356 Yeah. So this one is Incognito.
02:49:06.406 --> 02:49:06.946 Oh, OK.
02:49:07.026 --> 02:49:09.996 Right. Yeah. That's why I went back to here. Yeah.
02:49:08.176 --> 02:49:11.089 And this one and this one, the job seeker that actually works.
02:49:10.766 --> 02:49:11.116 Yeah.
02:49:11.089 --> 02:49:11.506 OK, cool.
02:49:11.806 --> 02:49:12.126 Yeah.
02:49:13.476 --> 02:49:17.356 Uh, yeah, that's a I made that mistake once, right?
02:49:18.676 --> 02:49:19.956 Why is my extended?
02:49:20.776 --> 02:49:21.836 Clipboard not working.
02:49:23.526 --> 02:49:25.826 What is happening? Why is it doing that?
02:49:35.346 --> 02:49:36.946 Cheeks, it was like.
02:49:38.866 --> 02:49:41.936 Doing something freaking? I'll tell you, dude.
02:49:43.546 --> 02:49:46.036 LastPass is not been working well for me lately.
02:49:47.046 --> 02:49:47.356 Yeah.
02:49:51.466 --> 02:49:51.896 OK.
02:49:52.516 --> 02:49:56.726 So index the thingies. Let's let's clear this thingy.
02:49:58.516 --> 02:49:58.886 Right.
02:50:00.066 --> 02:50:00.696 Hmm.
02:50:02.246 --> 02:50:04.056 Couldn't have said it better myself.
02:50:05.306 --> 02:50:08.586 And let's let's go ahead and refresh this thing.
02:50:11.156 --> 02:50:11.736 And.
02:50:12.476 --> 02:50:15.751 Because this is going to clear because Darian is not up here in
02:50:15.751 --> 02:50:15.956 the.
02:50:16.506 --> 02:50:16.916 Yeah.
02:50:18.396 --> 02:50:19.006 URL.
02:50:22.126 --> 02:50:24.385 Not only are probably going to want to run it to take a look
02:50:24.385 --> 02:50:24.496 at.
02:50:25.426 --> 02:50:28.340 Umm. If we can get like hero or someone on the I don't. I don't
02:50:28.340 --> 02:50:31.208 remember who's the front end or for this project. I think it's
02:50:31.208 --> 02:50:31.436 hero.
02:50:32.826 --> 02:50:35.467 Well, it's technically me. Heroes got a couple of things,
02:50:35.467 --> 02:50:38.337 but he got bogged down and see MC. So I have all the front end
02:50:38.337 --> 02:50:39.066 tickets as well.
02:50:39.736 --> 02:50:40.326 Nice.
02:50:41.266 --> 02:50:43.716 Yeah. So now it's try.
02:50:45.616 --> 02:50:46.286 Darien.
02:50:46.846 --> 02:50:52.999 Ah, on buddy. Two cities. Look at that. That's what I'm talking
02:50:48.426 --> 02:50:49.026 Boom.
02:50:49.786 --> 02:50:50.706 Own Jack.
02:50:51.686 --> 02:50:52.446 Yahtzee.
02:50:52.999 --> 02:50:53.576 about.
02:50:54.606 --> 02:50:55.516 Let's try Austin.
02:50:57.976 --> 02:50:59.426 We got two for Austin.
02:51:00.196 --> 02:51:03.906 Alright, well, it's clear all and look around a bit and see.
02:51:01.406 --> 02:51:02.196 It's clear that.
02:51:04.986 --> 02:51:05.636 Why?
02:51:05.476 --> 02:51:07.356 Service Hattiesburg.
02:51:08.846 --> 02:51:10.666 There's one Austin right there.
02:51:09.106 --> 02:51:10.436 There's one for Austin.
02:51:27.946 --> 02:51:30.746 That might be all the austins there's two austins.
02:51:29.736 --> 02:51:31.906 There, there really was only too Austins.
02:51:33.206 --> 02:51:37.405 OK, cool. All right, I thought there were three earlier, but
02:51:33.686 --> 02:51:36.446 Yeah, yeah. I think it's telling the truth.
02:51:37.286 --> 02:51:39.166 Yeah, it's closed. Let's try.
02:51:37.405 --> 02:51:39.746 yeah, I saw a bunch of hartfords.
02:51:45.586 --> 02:51:47.316 Well, two hartfords. Wait.
02:51:47.056 --> 02:51:49.404 Maybe I only saw it. Oh, it hasn't loaded yet. Click the
02:51:49.404 --> 02:51:50.476 search. OK, there it goes.
02:51:50.106 --> 02:51:50.406 Well.
02:51:51.656 --> 02:51:52.396 Yeah, there we go.
02:51:52.896 --> 02:51:54.776 OK, there's like four of them. Yeah. OK.
02:51:53.646 --> 02:51:54.466 4 Hartford.
02:51:55.396 --> 02:51:58.506 Yeah. Yeah, yeah, yeah. So cities working again.
02:51:59.186 --> 02:51:59.886 Let's try.
02:52:07.286 --> 02:52:07.706 Nothing.
02:52:09.426 --> 02:52:09.916 Hmm.
02:52:12.256 --> 02:52:14.756 There's definitely premium. Well, that's premium company.
02:52:16.646 --> 02:52:19.516 So it's like exact, right? Like you gotta.
02:52:24.526 --> 02:52:27.366 Premium company premium company premium company.
02:52:28.416 --> 02:52:29.316 That's exact.
02:52:31.206 --> 02:52:34.466 So if we go back, we do lower case premium company.
02:52:31.776 --> 02:52:35.106 Hmm. And the word and the word premium doesn't get it.
02:52:38.916 --> 02:52:39.626 That worked.
02:52:40.196 --> 02:52:43.161 And but it also got premium company name which it didn't get
02:52:43.161 --> 02:52:43.696 previously.
02:52:44.466 --> 02:52:45.316 That's true.
02:52:51.676 --> 02:52:53.416 Deluxe company. Wow, there's a lot of.
02:52:55.266 --> 02:52:56.636 Not cool company names.
02:52:57.546 --> 02:52:57.926 Nothing.
02:53:01.576 --> 02:53:05.164 Supreme Company, actually, that's probably a real company
02:53:05.164 --> 02:53:07.516 cause that overpriced clothing brand.
02:53:08.306 --> 02:53:11.100 Yes, I went to the mall last night to finish up Christmas
02:53:11.100 --> 02:53:13.943 shopping and I saw a Supreme branded mini fridge and I was
02:53:13.943 --> 02:53:16.256 like, that's probably like 2-3 million dollars.
02:53:17.796 --> 02:53:21.570 Honestly, if I was in any, if I was in any, actually I think
02:53:17.966 --> 02:53:19.216 I didn't. I couldn't see.
02:53:21.570 --> 02:53:25.468 this is a thing in Spain because they're copy. I think they're
02:53:25.468 --> 02:53:28.995 like whatever laws work differently. Someone just, like,
02:53:27.326 --> 02:53:27.636 Yeah.
02:53:28.995 --> 02:53:32.955 incorporated supreme and Spain. And just as selling a bunch of,
02:53:32.955 --> 02:53:35.616 like, knock off stuff there and it's like.
02:53:34.406 --> 02:53:37.416 Knock off crap for like $10,000. What a legend.
02:53:38.616 --> 02:53:42.420 That's what I do like if I lived in something like nice country
02:53:40.036 --> 02:53:40.786 Yeah.
02:53:42.420 --> 02:53:46.106 where the laws were like back, it's like first to file versus
02:53:46.106 --> 02:53:49.553 first to actually like do something. So Spain is first to
02:53:47.616 --> 02:53:48.006 Right.
02:53:49.553 --> 02:53:53.417 file. So they filed for all the copyright ship before the actual
02:53:53.417 --> 02:53:57.103 company did. So they can just sell as much supreme stuff they
02:53:57.103 --> 02:53:57.876 as they want.
02:53:58.986 --> 02:54:00.206 Out of state, it's funny.
02:54:02.076 --> 02:54:05.486 It's taking forever in the day to load these images in.
02:54:06.276 --> 02:54:09.361 I should I should do that, move to Europe. Some country that's
02:54:06.306 --> 02:54:07.206 That's what.
02:54:09.361 --> 02:54:12.446 first of all, I'll just start selling Gucci and supreme stuff.
02:54:13.906 --> 02:54:16.556 Just sit back and enjoy life.
02:54:23.436 --> 02:54:26.466 The the ad carousel hasn't even loaded in yet.
02:54:36.616 --> 02:54:38.386 There, it's coming. There's the buttons.
02:54:40.776 --> 02:54:43.046 They're ooh, ooh, boom boom.
02:54:41.836 --> 02:54:44.026 Ohh two of them. Yeah, there they go.
02:54:44.726 --> 02:54:48.108 And here in just a second, when the pictures load for the rest
02:54:48.108 --> 02:54:48.806 of the pages.
02:54:49.656 --> 02:54:51.936 And the rest of the ads? This will stop spinning.
02:54:54.486 --> 02:54:56.426 That's why it spins for so long.
02:54:57.866 --> 02:54:58.196 Done.
02:54:57.936 --> 02:55:01.433 Because it actually wasn't done loading stuff. Change your
02:55:01.433 --> 02:55:04.931 filter in the in the dev tools to all remove the fetch XHR
02:55:04.931 --> 02:55:05.346 filter.
02:55:08.156 --> 02:55:11.596 Scroll around and I don't see any of those images in here.
02:55:12.666 --> 02:55:13.866 Other there, they're all the bottom.
02:55:33.366 --> 02:55:34.616 Those are cached, right?
02:55:37.156 --> 02:55:37.666 Yeah.
02:55:38.456 --> 02:55:41.366 You, even though you have disabled cache and it will.
02:55:43.696 --> 02:55:45.886 Oh, those are hard coded images.
02:55:47.496 --> 02:55:49.756 That's why because it's like SVG in the code.
02:55:48.396 --> 02:55:48.746 So.
02:55:51.006 --> 02:55:52.746 So it's not even that it's like.
02:55:51.686 --> 02:55:52.266 Where is the.
02:55:53.696 --> 02:55:56.795 It's very interesting that it's not that it's taking that long
02:55:56.795 --> 02:55:59.796 to load, it's that it's taking forever to even request them.
02:56:00.806 --> 02:56:01.576 Yeah.
02:56:06.726 --> 02:56:09.336 Uh gosh, we're gonna be sitting here for a minute.
02:56:25.726 --> 02:56:30.019 So the ones on the job postings are coming from account images.
02:56:30.019 --> 02:56:33.776 The ones on the ad carousel are coming from add images.
02:56:34.746 --> 02:56:35.506 That makes sense.
02:56:37.556 --> 02:56:41.103 It's only requested one. That's far Ohh cause I guess it's the
02:56:41.103 --> 02:56:41.666 same well.
02:56:43.086 --> 02:56:45.706 We should see a call. I don't know. Should we see a call?
02:56:45.706 --> 02:56:48.461 Yeah, we should see a call for each image, right? Yeah. Here
02:56:48.461 --> 02:56:51.217 they. Well. No, they're coming in up there, but we don't see
02:56:51.217 --> 02:56:52.166 the calls that there.
02:56:53.696 --> 02:56:54.686 But just one call.
02:56:56.696 --> 02:56:57.806 Because it's the same image.
02:56:58.306 --> 02:57:01.418 Yeah, probably recognize that they're the same image and just
02:57:01.418 --> 02:57:03.276 serves the one that's already there.
02:57:04.976 --> 02:57:07.156 Yeah, it just takes some forever to populate up here.
02:57:09.546 --> 02:57:11.996 Something is not right about that.
02:57:13.036 --> 02:57:15.096 With that, carousels point in the images.
02:57:17.846 --> 02:57:20.516 **** man, I don't really know what to do.
02:57:22.136 --> 02:57:24.662 Yeah, that one. We're probably gonna want front end here to
02:57:24.662 --> 02:57:26.136 look at again because I'm I'm not.
02:57:28.336 --> 02:57:31.872 I'm not super familiar with the with what might be causing
02:57:28.406 --> 02:57:29.856 Yeah. So let's just.
02:57:31.872 --> 02:57:35.708 images to not even be requested for that long. There's gotta be
02:57:35.708 --> 02:57:38.466 something in like the React code that's just.
02:57:40.236 --> 02:57:41.006 Weirdly.
02:57:41.286 --> 02:57:41.696 Yeah.
02:57:42.946 --> 02:57:44.066 Delayed or something?
02:57:43.506 --> 02:57:44.216 Well.
02:57:47.426 --> 02:57:52.136 So if we take a little ***** ** **** Sprint board.
02:57:56.176 --> 02:57:58.566 I wonder if it's related to the.
02:58:00.236 --> 02:58:01.996 I'm gonna go ahead and kill the recording here.